3 ms·
i never run into these issues in >100k loc of productionized llm generated elixir (nil safety, type issues). i wonder, is there something architecturally in go
by dnautics 2mo ago
i never run into these issues in >100k loc of productionized llm generated elixir (nil safety, type issues). i wonder, is there something architecturally in go that makes this a particular problem?
- za3faran 2mo agoUp until quite recently, golang lacked generics, so `interface{}` was passed everywhere. It does not have typesafe enums (you can pass integers and it will compile). It has no way of declaring immutable structures. It does not have pattern matching.
- Mawr 2mo ago> It does not have typesafe enums (you can pass integers and it will compile). sigh. Sure, if you literally pass an untyped, hard-coded integer, like so: foo(100) then, and only then will it compile. However, this won't: a := 100 foo(a) How horrific.