"What should we actually call a Vec" - the greatest thread in the history of Rust, locked by a moderator after 12,239 pages of heated debate
-
-
Replying to @mgattozzi @sgrif and
C++ kinda sealed our fate on that one, I think I still maintain it should be ArrayBuf but whatever
1 reply 0 retweets 1 like -
Replying to @myrrlyn @mgattozzi and
I have problems with the word buffer, as well. Also array, really. I have the most problems with vector, though.
3 replies 0 retweets 1 like -
Replying to @ManishEarth @myrrlyn and
Array would have been an excellent name.
1 reply 0 retweets 1 like -
Replying to @sgrif @ManishEarth and
What would [T; N] be then? … Run, maybe?
1 reply 0 retweets 0 likes -
-
-
Although I guess Array isn't a named type anywhere either; it's just [T; some const] so
1 reply 0 retweets 0 likes -
Would we call [T] an unsized array? [T; n] - fixed size array Vec<T> - heap allocated, dynamically sized array [T] - unsized array &[T] - array slice
1 reply 0 retweets 0 likes -
Unsized slice
1 reply 0 retweets 2 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.