Sorry but how do you know we are a minority? I dislike the try proposal for
all the reasons already mentioned by others.
I did fill out the survey but I do not remember there being an option to
say this simple thing.
While I dislike the verbose error handling it's many times better than
introducing flow of control constructs.
It's unusual for people to complain about the things that don't bother them.
So I was quiet on the topic then - I am not now.
Some of us had to fix so much broken java/python code with invisible and
anonymous goto statements (aka exceptions) that even just seeing the
keyword try prompts a physical reaction.
On Saturday, June 29, 2019 at 8:15:12 PM UTC, andrey mirtchovski wrote:
>
> > This issue seems to have resonated with a lot of people, which may be an
> important data point when considering the try proposal
>
> Where were all those people when the Go Surveys were being taken the
> last few years? Overwhelmingly, the people have voted error handling
> as a major issue. The voters may not be intimately involved with Go
> development and may not be willing to produce proposals, but the votes
> are there and speak loudly. A vocal minority skewing the proposals
> with downvotes should not be a cause to abscond something that server
> the greater good.
>
> If the status quo can not be breached, the worst we can do is another
> round of the Go Survey and vocally invite everyone to participate.
>
> On Sat, Jun 29, 2019 at 2:03 PM Burak Serdar <bse...@ieee.org
> <javascript:>> wrote:
> >
> > On Sat, Jun 29, 2019 at 1:45 PM Robert Engels <ren...@ix.netcom.com
> <javascript:>> wrote:
> > >
> > > If you don’t understand the history you are doomed to repeat it. The
> ‘try’ proposal is barely better than the current situation. There is as a
> reason exception handling with try catch was designed along with OO. It
> simplifies error handling immensely. “Try” as you might, you might think
> you are improving on it, but you’re not.
> >
> > I think try-catch simplifies writing error handling code, but not
> > necessarily simplifies understanding or modifying it once it is
> > written.
> >
> > I, too, like the if err!=nil {} as it is. One improvement I can think
> > of is reducing the boilerplate by implementing a macro-like
> > extension:
> >
> > func f() {
> > handle openErr(err) error {
> > return err
> > }
> > x, openErr:=os.Open(...)
> >
> > openErr would be called if the error is non-nil. Some months ago I did
> > write a proposal similar to this, and I was not the only one thinking
> > along the same lines. It is backward compatible, and the code is still
> > readable in my opinion.
> >
> >
> >
> > >
> > > Go should implement caught exceptions and be done with it. Stop trying
> to be cute. Take what works elsewhere and stop thinking you’re always the
> smartest person in the room.
> > >
> > > On Jun 29, 2019, at 2:35 PM, Tyler Compton <xav...@gmail.com
> <javascript:>> wrote:
> > >
> > > Sorry, forgot to CC on my last email. Here it is again:
> > >
> > >> And you must understand the specific: you are solving relatively hard
> problems developing language called Go with low mistake cost and we are
> solving simple problems with a DSL called Go but our mistake cost is much
> higher than yours.
> > >
> > >
> > > Sorry, I'm not sure I understand. Who is the "you" and "we" in these
> circumstances? I should be clear, I'm not a Go core team member and I had
> nothing to do with the creation of the original "try" proposal. I've just
> been involved in the proposal and anti-proposal discussion and noticed a
> shift in tone.
> > >
> > >> I thought you are trying to be as practical as possible making a
> language with such a retarded yet somehow usable type system in XXI. But
> this recent proposal raises some suspicions...
> > >
> > >
> > > What is XXI? Are you referring to Go's type system?
> > >
> > > On Sat, Jun 29, 2019 at 12:18 PM Denis Cheremisov <
> denis.c...@gmail.com <javascript:>> wrote:
> > >>
> > >> And prepare for wider audience in shitty “try” proposal after 1 July.
> > >>
> > >> --
> > >> You received this message because you are subscribed to the Google
> Groups "golang-nuts" group.
> > >> To unsubscribe from this group and stop receiving emails from it,
> send an email to golan...@googlegroups.com <javascript:>.
> > >> To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-nuts/c99b3572-427c-4b7d-91ff-2fb4e4cb9177%40googlegroups.com.
>
>
> > >> For more options, visit https://groups.google.com/d/optout.
> > >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups "golang-nuts" group.
> > > To unsubscribe from this group and stop receiving emails from it, send
> an email to golan...@googlegroups.com <javascript:>.
> > > To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-nuts/CAA%3DXfu031bDbJheZ5-JUbsea1%2BYAn68dfO5ve8pn4T7%3DRFxqRQ%40mail.gmail.com.
>
>
> > > For more options, visit https://groups.google.com/d/optout.
> > >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups "golang-nuts" group.
> > > To unsubscribe from this group and stop receiving emails from it, send
> an email to golan...@googlegroups.com <javascript:>.
> > > To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-nuts/A4B77F76-E16F-4AE0-AAD4-29C553F079B0%40ix.netcom.com.
>
>
> > > For more options, visit https://groups.google.com/d/optout.
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "golang-nuts" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to golan...@googlegroups.com <javascript:>.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-nuts/CAMV2Rqq%2BeOZoyEVj-p%3DXJE3%3DUeA%2B%2B5ZLrTLp-SdxqVhxOqec9g%40mail.gmail.com.
>
>
> > For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/f5b5afaf-0d55-4011-9b72-7258a9750a28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
