semisol @semisol - 1d
NFDB progress: I hate the Go bindings and therefore am forking them
mleku @mleku - 1d
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
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
it's kinda funny how Go is like that... like, bitch, you can write C++, go is like less than half as complicated the only area that go is a bit funny is when you need to sanitize secrets, but there is memguard and it's not difficult to cast an immutable string to bytes and zero it also (i just did this the other day for my bunker signer project) the memory handling in the bitcoin core secp256k1 library is also ugly and retarded too... it keeps the secret and both coordinates of the public key in a 96 byte long array, and i could not find the X-only ECDH function either, i hope to fix that in the near future so i can use my go library for nostr cryptography with a noise framework network transport encoder
