3 ms·
My point is that between Go's custom compiler backend and inexpressive typing there's much more need to build things like this in directly vs what other languag
by staticassertion 5y ago
My point is that between Go's custom compiler backend and inexpressive typing there's much more need to build things like this in directly vs what other languages can do by just using llvm/gcc. Like if Go developers want sanitizers equivalent to what llvm packages they'll have to build that themselves, although that won't have the same issue with inexpressive types.
- aleksi 5y ago> Like if Go developers want sanitizers equivalent to what llvm packages they'll have to build that themselves Go uses LLVM’s ThreadSanitizer since 1.1.
- staticassertion 5y agoI don't think that really addresses my point, it just shows that they did the work for one sanitizer already.