On 12-06-12 3:28 PM, Niko Matsakis wrote:
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.
Totally agree. Though it'll make my skin crawl to see *foo all over rust code, I'll learn to think of them as "proven-live pointers" eventually :)
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.
Try sketching some code in a buffer, see how it looks. Might be possible to come up with an abbreviation (!T perhaps, or the old unused sigil ?T maybe?), might be possible for inference and a couple rules about the boundaries of extern functions to fill in the details.
-Graydon _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
