Filippo Valsorda
Filippo Valsorda
We realized a GODEBUG is actually a security risk here: most programs will start to ignore errors from Read because they can't happen (which is the intended behavior), but then...
> are there processors with 128-bit integer multiply and divide instructions There are instructions that let you multiply two 64-bit registers to two 64-bit registers. Having access to those in...
> [...] Unfortunately, this requires writing assembly, because writing high-performance arithmetic is not possible in Go — it's simply not a design goal of the language. (There are a few...
(By the way, #24813 seems to be working well for the cryptography use case, so we don't really need the uint128 type for that anymore.)
@fd0 you're right, the best thing to do is to always ignore the signal, and do complete error handling + cleanup on EPIPE (or any other non-Timeout) errors from stdin/out/err....
For standard library development I use toolsGopath to keep separate builds of the tools in case tip introduced any incompatibility. How would that use case be handled if the option...
#351 Looks like we didn't implement the warning...
I believe this was intentional in 9dd6af1f6d30fc79fb0d972394deebdabad6b5eb, because there is no reliable way to tell if a request came in over HTTPS or HTTP, it assumes it's HTTPS to fail...
Using these to develop the Go implementation of ML-DSA, thank you @gendx!
There's a concrete proposal at https://go.dev/cl/620795, but I'd like guidance from @golang/runtime if that's the right way to go about it. I found some padding in the g struct to...