On 09/12/2012 02:54 PM, Brian Anderson wrote:
'unsafe' is the final holdout keyword that can still be used as an
ident, and we love using it as a module name: core::unsafe,
core::vec::unsafe, core::str::unsafe, core::at_vec::unsafe.
So I don't have any great ideas. Do you?
I'm going to
'unsafe' is the final holdout keyword that can still be used as an
ident, and we love using it as a module name: core::unsafe,
core::vec::unsafe, core::str::unsafe, core::at_vec::unsafe.
In order to convert 'unsafe' to a true keyword we need a different
strategy for coralling unsafe
On 9/12/12 2:54 PM, Brian Anderson wrote:
So I don't have any great ideas. Do you?
raw? lowlevel (ll)? machine? sys?
Patrick
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev
+1 for sys or system.
--
Ziad
On Wed, Sep 12, 2012 at 2:55 PM, Patrick Walton pwal...@mozilla.com wrote:
On 9/12/12 2:54 PM, Brian Anderson wrote:
So I don't have any great ideas. Do you?
raw? lowlevel (ll)? machine? sys?
Patrick
__**_
On 12-09-12 2:55 PM, Patrick Walton wrote:
On 9/12/12 2:54 PM, Brian Anderson wrote:
So I don't have any great ideas. Do you?
raw? lowlevel (ll)? machine? sys?
I think 'raw' is good here; also a slightly less clunky word for the
*foo pointer type: 'raw pointer'. They're not always unsafe,
