No, we can just *see* the "if err != nil". It's still there in Java or Ruby or P... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		JulianMorrison on Aug 19, 2013 \| parent \| context \| favorite \| on: Rewriting a large production system in Go No, we can just see the "if err != nil". It's still there in Java or Ruby or Python, lurking in the notional space between the lines and waiting to branch to an exception handler you installed in the caller's caller's caller.

pcwalton on Aug 19, 2013 [–]

Same in Go, because of panic and recover. For example, "foo.Bar", if foo is a nil pointer, can invisibly branch to an exception handler you installed in the caller's caller's caller.

JulianMorrison on Aug 19, 2013 | [–]

Can but idiomatically, usually does not. In most code, that would behave like a segfault with a more helpful crash log.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact