5 ms·
>Go is unsound (Go slices...) What are you referring to here? Go's current slice implementation could only possibly introduce unsoundness via data races. Even
by foldr 1y ago
>Go is unsound (Go slices...)
What are you referring to here? Go's current slice implementation could only possibly introduce unsoundness via data races. Even there, I think you might actually need to muck around with an interface value rather than a slice to demonstrate unsoundness of the type system (rather than just memory corruption or unsafe memory access).
Typescript's type system is just deliberately unsound by design (for defensible reasons). It's a whole nother level of unsoundness in comparison to Go.
- LoganDark 1y ago> What are you referring to here? In this case my use of "unsound" is somewhat stretched to "particularly easy to make subtle mistakes as a programmer": https://www.reddit.com/r/golang/comments/1h5ws8e/comment/m09pzcu/ https://www.reddit.com/r/golang/comments/1h5ws8e/comment/m09... https://build-your-own.org/blog/20241125_go_slice_surprise/ https://build-your-own.org/blog/20241125_go_slice_surprise/