I know that in Go a data race is undefined behavior. How likely is the undefined behavior likely to result in an exploitable security bug, where "exploitable" means more than just denial-of-service? I am looking for qualitative estimates here. Is it the kind of bug that would be almost impossible to exploit, or could a reliable exploit be crafted?
If the former, then Go is a good choice for security-critical applications; if the latter, then I should probably choose a language which provides a compile-time guarantee that data races will not happen (safe Rust/@safe D) or at least guarantees that they will not result in memory corruption (.NET Core/Haskell) -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
