[rust-dev] Closure types and iterators: impossible constraints?

2014-01-19 Thread Abraham Egnor
I recently ran into an issue with closure types that seems to have no solution present in the language. In a silly example, say you want to implement an iterator that wraps an int iterator and adds a value to it: fn add_nI: IteratorInt(v: I, n: int) - ??? This is naturally expressed as a map

Re: [rust-dev] Closure types and iterators: impossible constraints?

2014-01-19 Thread Abraham Egnor
Aha, yes, that would plug the hole. I'm a little worried that there's no assignee and no milestone listed, and the only mention of a timeline on that page is a comment of Not until Rust 2.0. Is that comment accurate? That's a fairly major feature to leave lacking, especially given the effect of

[rust-dev] Questions from a newcomer

2014-01-12 Thread Abraham Egnor
Hello! The 0.9 release prompted me to poke at my nascent rust code. Very impressed with the language and the progress since I last looked (0.4 maybe?). Some questions that I wasn't able to find answers for: * Is there any built-in way to iterate over all values of a C-like enum? It's not hard

Re: [rust-dev] Questions from a newcomer

2014-01-12 Thread Abraham Egnor
Oh yes, and one more: * Why does the do-notation require a function that takes a proc()? Given that || is the recommended type for HOFs it seems like it would be much more convenient if it worked with functions expecting a proc() or a ||. On Sun, Jan 12, 2014 at 8:09 AM, Abraham Egnor abe.eg