Here's another one: The fact that, when changing a tag variant, you
have to update every single place that matches against it. We might
want to revisit the idea of named variant args, that you match by
name, so that A) you can leave off all the '_' placeholders, and B)
you only need to update your
On Thu, Dec 22, 2011 at 11:55 AM, Graydon Hoare gray...@mozilla.com wrote:
On 11-12-21 09:10 PM, Joe Groff wrote:
1. I support being able to drop mandatory literal type specifiers on
values that are within the range of their expected type
Related: I'd like contributed source
On 11-12-20 02:55 PM, Elly Jones wrote:
2. The dot after the nullary tag. In general I want to write a nullary tag a LOT
more often than I want to write a wildcard binder, so I feel like this is the
wrong way for this choice to go, but I'll understand if this is a decided issue
already.
and there'll always be that one jerk on your team who runs their literals
together without the separator.
*raises hand*
But seriously, I think that if our approach to type inference
supported it, inferring the type of literals (with warning for
overflows) would be great. But it doesn't -- or
On 11-12-22 04:27 PM, Patrick Walton wrote:
I would really like to advocate once again for Standard ML's solution: simply
disambiguate variable bindings and tag constructors at the name resolution
phase.
Yeah. I'm not as horrified by this as I was the first time I heard it.
Especially now
Hi,
I've changed the interpretation of 'log' a bit, and removed log_err.
Since this is relatively user-visible I thought I'd mention it here.
Full detail is in the end of the bug:
https://github.com/graydon/rust/issues/1087
I'll update documentation tomorrow.
-Graydon
