• 1 Post
  • 34 Comments
Joined 11 months ago
cake
Cake day: August 18th, 2023

help-circle









  • Ah. No, keep reading:

    In a less than optimal world, you might decide to do something less inspired. You might take that break from the C runtime and then just implement threads again, with basically the same semantics, except that they are scheduled in userspace. Your users would be required to implement concurrency in terms of threads, locks and channels, just like they had always been in the past. You might also decide your language should have other classic features like null pointers, default constructors, data races and GOTO, for reasons known only to you. Maybe you would also drag your feet for years on adding generics, despite frequent user requests. You might go do that, in a less than optimal world.

    (Emphasis on “go” is in the original.)








  • Go if you want a real mental challenge

    I don’t mean to be rude, but I find this baffling; what do you mean by it? One of the primary design goals of Go is to be simple to learn (this is fairly well documented), and it’s one of the few things I really have to give the language credit for. Rob Pike has specifically discussed wanting it to be accessible to recent CS graduates who have mostly used Java. I have never heard anyone before describe learning Go as a “challenge.”



  • You’re misunderstanding the posts you’re explaining. Sanitizers, including ASan, HWASan, and bound sanitizer, are not “static analysis tools”. They are runtime tools, which is why they have a performance impact. They’re not intended to be deployed as part of a final executable.

    I don’t know how you can read this sentence and interpret it to mean that they “haven’t onboarded AddressSanitizer”:

    In previous years our memory bug detection efforts were focused on Address Sanitizer (ASan).