Hacker News Reader

"Impure function calls in pure functions are detected and raise errors at runtime."

Is there value in having a pure/impure distinction when all pure functions end up needing a try/catch around them?

Yes - you can run unit tests? Still not the best, and compile-time would be better, but I'm not sure that's achievable in golang.

Can you elaborate a bit on what you mean?

It seems like this distinction could be done at compile time instead of at runtime.

Ah okay, makes sense.