so often these things are written like java with VeryFuckingLongNames_AndSnake_Case_As_Well

ugly fucking shit, it's like, bitch, did you not read the Go guides to good idiom??? ugh... openapi generator is like that too, identifiers that are over 32 characters are from the Devil

Reply to this note

Please Login to reply.

Discussion

they used GC cleanup functions for cleaning up C++ promises which did not always work and led to memory leaks

the future API now has an internal cache state

now the future value is automatically copied into Go-space and cached in the future struct once you do Get()

it will automatically release the future as well when you run Get() or Cancel() as it is no longer needed because you either already have the value cached now or discarded the result