On Fri, Feb 22, 2013 at 12:35 PM, John Clements <cleme...@brinckerhoff.org> wrote: > > On Feb 22, 2013, at 6:22 AM, Paul Stansifer wrote: > > > Rust syntax expects a literal number in the `[T * n]` construct; from the > > parser's point of view, what it receives is an expression, without any > > information that it is a number. (There are internal reasons for this, but > > it also makes the behavior of `$` more consistent; for example, preventing > > Rust from having C's issue where everybody has to use lots of parentheses > > in macro definitions.) Implementing $n:integer in Rust is a possible > > solution, but not likely to happen very soon. > > > > Unfortunately, I can't think of a workaround that generates the same type. > > More or less as a note to myself and Paul: I claim that this problem would be > solved by a token-tree-based macro system. > > John >
I just want to add for consideration: I hope the (eventually) implemented solution allows compile-time evaluable integer expressions for maximal expressivity. Same thing for $n:bool, etc, if implemented. Thanks, Ashish _______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
