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?
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.