Re: [rust-dev] The new way to do iteration

2011-10-25 Thread Brian Anderson
On 10/25/2011 12:52 AM, Marijn Haverbeke wrote: This seems to make the feature not very useful. Is there a way we can get around this limitation? Why do you say that? It is trivial to get around this limitation, but it seems that block calls like this in expression position would just look even

Re: [rust-dev] Change the syntax for type parameter kinds?

2011-10-25 Thread Marijn Haverbeke
I implemented this today. The rationale for making T represent 'pinned' is that 'pinned' is the broadest category -- all types can be passed to a function expecting a pinned type. I still think that making the default 'shared' is a good idea, but there are downsides -- it's easy to define a generic

Re: [rust-dev] The new way to do iteration

2011-10-25 Thread Marijn Haverbeke
> Does this mean that the little code snippet on > http://www.rust-lang.org/ is no longer valid? No, that's a vector for loop. Only 'for each x in myiter() { ... }' was removed. ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/list

Re: [rust-dev] The new way to do iteration

2011-10-25 Thread Marijn Haverbeke
> This seems to make the feature not very useful. Is there a way we can get > around this limitation? Why do you say that? It is trivial to get around this limitation, but it seems that block calls like this in expression position would just look even weirder than the form where you have the block