4 ms·
~ for allocation was weird, but I will miss lack of ~ as analogy to * . Will they change * to `RawPointer<T>` too? ;) I'm not happy about change of [T] to Vec
by pornel 13y ago
~ for allocation was weird, but I will miss lack of ~ as analogy to * .
Will they change * to `RawPointer<T>` too? ;)
I'm not happy about change of [T] to Vec<T> either.
I hope all these changes will make a full circle and get a first-class syntax back.
- illicium 13y ago>first-class syntax Perl-y symbol nonsense is not a first-class syntax
- tormeh 13y agoI agree. Syntax should be descriptive first and concise second.
- tomjakubowski 13y ago> I'm not happy about change of [T] to Vec<T> either. [T] wasn't a thing in Rust. ~[T] hasn't gone and won't go away either. See this email from acrichton: https://mail.mozilla.org/pipermail/rust-dev/2014-April/009352.html https://mail.mozilla.org/pipermail/rust-dev/2014-April/00935...
- dbaupp 13y agoThat email is somewhat outdated. ~[T] is certainly disappearing with that syntax, becoming Box<[T]>, andthere has been much back and forth about whether this Box<[T]> type actually offers anything over Vec<T>, or if it's just a "cute" consequence of the type system. (The borrowed slices &[T] and &mut [T] are certainly here to stay.)
- lazzlazzlazz 13y ago> a first-class syntax back. I would argue that this change elevates the clarity and quality of Rust syntax.