3 ms·
3x more bugs that you know about. I wouldn't be surprised if Go's static type system just found more bugs, and the Python program had just as many bugs but you
by IshKebab 8y ago
3x more bugs that you know about. I wouldn't be surprised if Go's static type system just found more bugs, and the Python program had just as many bugs but you didn't happen to hit them at runtime.
- bb88 8y agoI would assume he's talking about non-type system bugs. In 2018, most people won't look at a PR unless it compiles and the unit tests works.
- danpalmer 8y agoI got the impression these were bugs that made it into a tracker of some sort, and I don’t think most engineers log “bugs” they encounter during local development before some notion of a release (be it to staging, the world, the master branch, whatever).
- zzzcpan 8y agoGo static type system doesn't find bugs a Python program might have, but introduces plenty of possibilities for bugs too.
- PeterisP 8y agoCan you elaborate about types of bugs that are caused by a static type system, about extra possibilities introduced by it? There are many commonly understood disadvantages of static type systems, but extra possibilities for bugs usually isn't among them.
- nwmcsween 8y agoThe type system has to support the language features, there are tons or races, deadlocks etc due to go language features without a type system to express these features.