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

https://code.google.com/p/go/issues/detail?id=65



Don't just link that with no comment. I thought you were disagreeing, not just showing that the go people have refused to fix it for two years.

-----


To be fair, they have executed the overall project very well from what I've seen. A few things falling through the cracks is probably inevitable. That issue's not closed so there's hope for it yet.

-----


OK, here's the expanded text for my comment (I didn't "show something" or disagree/agree -- I just provided reference):

"Here's this issue in Go bug tracker: https://code.google.com/p/go/issues/detail?id=65

-----


Providing a link to the issue in the bugtracker, with discussion, is definitely "showing something".

I don't know, maybe I'm just weird, but when I see a comment replied to with a single link patterns suggest that it's a link disproving something. So I got confused until I had read the full page.

-----


Is seems to be a bug but it could well be a feature. Requiring that functions end with a return statement is a good thing IMO. That avoids weird bugs if later the "else" is replaced by an "else if".

-----




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: