5 ms·
> Stack traces are desperately needed to give errors context, and I was very disappointed to see that proposal dropped from Go 1.13. At the same time, I'm hesi
by aikah 7y ago
> Stack traces are desperately needed to give errors context, and I was very disappointed to see that proposal dropped from Go 1.13. At the same time, I'm hesitant to use xerrors in production code because it's likely to change rapidly in the future.
By the way what's left of all the "Go 2" proposals? "generics" look like they are in limbo and so is the "try/catch" proposal. Has anything been implemented yet?
- weberc2 7y agoPretty sure the try proposal was killed. Generics hasn’t seen much headway to my knowledge. Not sure what’s up with it.
- xienze 7y ago> Generics hasn’t seen much headway to my knowledge. Not sure what’s up with it. They don't want to do generics, they never have.
- ithkuil 7y agoSo you know for sure that consensus around https://go.googlesource.com/proposal/+/master/design/go2draft-contracts.md https://go.googlesource.com/proposal/+/master/design/go2draf... is impossible to reach?
- earthboundkid 7y agoI have no inside knowledge, but my guess as an observer is they’re just plugging away at implementation behind the scenes and some descendent of that proposal will be what ships.