[ On | No ] syntactic support for error handling - The Go Programming Language

Go team plans around error handling support

@h4ckernews “The Go team takes community feedback seriously”, yeah, knowing the company it came from, I'm going to go with “um, no it doesn't.” Otherwise, they would have added a proper exception system by now.
@quatrava @h4ckernews what exactly is that proper exception system and have you read the discussions under various error handling design proposals? I definitely do not want try-catch in Go, the reasons why it's not in the language have been articulated well enough. And variations of this are what "exception system" imply.
@bmarinov @h4ckernews this is not exactly a new topic, I suggest you read https://news.ycombinator.com/item?id=4159641 for instance — I'm sure a Google search would reveal more. On the other hand, I do think that requesting dissenters to read some internal diatribes penned by people who may or may not be informed about what exceptions are and how to compile them correctly, is totally on-brand for this ecosystem as per my previous comment. My plate is full of that with Python's PEPs already, so no thanks.
@quatrava @h4ckernews what I meant that there have been numerous proposals and discussions in the open. So if you have a good suggestion which takes language design and current concerns into consideration, feel free to specify in some detail how it would work.
Claiming that they should just fix it with an "exception system" is the opposite of that. The group of people which do not like go errors mostly overlaps with people which want pretty code above readable sad path. There is nothing wrong with exceptions and cimilar approaches, just.. Not in this language, tyvm.