On 6/12/12 3:28 PM, Niko Matsakis wrote:
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.

What if pointers in native function signatures were implicitly unsafe? C has no concept of regions anyhow...

Patrick

_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev

Reply via email to