On 12/2/13 1:16 AM, Gaetan wrote:
if "do" makes the code more readable or more "beautiful", I higly recommend keeping this sugar syntax. If there are corner cases where do doesn't do the job, the developer should not use it in these cases.
The problem here is the closure inference, especially when custom smart pointers are concerned. Do you want the "do" syntax to start invoking arbitrary custom smart pointer constructors based on the type?
Patrick _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
