On 6/12/12 3:05 PM, Graydon Hoare wrote:
Anyway, I like this. This is a good target to aim for. Though perhaps .. given that you're saying you _do_ want & in a pattern to "eventually" mean by-ref binding, maybe just make it mean that from the get-go, and defer region-pointer patterns altogether until they can be written unambiguously as *, as you say here. Thoughts?
Seeing as we're not really using region types yet, it seems like NOW is the time to decide if we want to move to writing them as *T and so forth. I agree there is no sense in implement a change in patterns to go to an intermediate state that we already know is suboptimal.
It's a good point that *unsafe.T is rather noisy. I thought that was ok, but I wasn't thinking about the fact that it will appear often in FFIs. I am not sure how this would work out in practice. As you say, region ptrs in argument position are ok, but region ptrs in return position would yield inappropriate errors when calling the function.
Niko _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
