On 7/14/11 12:11 PM, Graydon Hoare wrote:
I disagree. The delete is the prohibited bit (by type-based interference with *h1; best the compiler can do due to the id() call it can't see through). Accessing &val in a read-only sense should be safe.
Okay, I see what you mean. I'm a bit concerned about function calls wildly trashing aliases due to the compiler being unable to see through them; makes me wonder if it's worth the complexity of aliasing into patterns as opposed to having pattern matching bindings simply copy (which would dramatically decrease alias usage, I think).
Patrick _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
