3 ms·
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
by niftich 10y ago
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 https://news.ycombinator.com/item?id=13566110
- cetxcz 10y agoThe 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.
- calcifer 10y agoTo 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.