Re:Declined Proposal: A built-in Go error check function, “try”
by UK-AL on Tuesday July 16, 2019 @09:45PM
(#20455689)
Honestly I think moving to towards Idris/coq level type systems saves more time in the long run.
Being close c means you discover errors at run time, then you have to come back to cover them.
Re:Declined Proposal: A built-in Go error check function, “try”
by bmurphy1976 on Tuesday July 16, 2019 @09:51PM
(#20455717)
For humongous projects or critically important ones I'd agree with you, but for smaller/mid sized projects I can't agree. I think it's total overkill in many instances.
Would be nice if there was a language that scaled from C to Idris gracefully, but C++ and Scala make me think that's a pipe dream.
I don't see this as an either/or situation. There's a continuum between do whatever the hell you want C and rigorously defined Idris code. Picking a spot on that line involves many trade-offs and everybody has to choose what's right for their situation. That means Go approach is sometimes superior to the Scala approach for a certain class of problems in certain domains.
Edit: don't downvote me, tell me how I'm wrong.