News for hackers. Stuff that matters.
Re:The State of Go by niftich on Sunday February 05, 2017 @12:33PM (#13573401)
Conversion rules seem like an awfully specific language feature to introduce just to scratch a very particular itch.

The rest of the slides are pretty standard-fare, and that's a good thing. Would've liked a reference to the lack of monotonic time, though; either an acknowledgment that it's a problem (because it's now fairly widely known), or a mention that a new proposal to fix it [1] is in the works.

[1] https://news.ycombinator.com/item?id=13566110

Re:The State of Go by cetxcz on Sunday February 05, 2017 @01:43PM (#13573787)
The conversion feature is in fact very convenient.

We often keep different types for what we get from the user (JSON) and what we write on the database (e.g: BSON). Having the ability to convert between them without having to re-type everything is useful for a lot of code out there.

Re:The State of Go by calcifer on Sunday February 05, 2017 @05:24PM (#13575043)
To be fair, you can do that right now with unsafe.Pointer, but of course it's better to have a compile time checked version of it.