Are any other @rustlang folks bothered by `Vec` over `Vector` but `Option` over `Opt`? (And a billion other things that are abbreviated that don't need to be)
-
-
I feel that vector is as bad or worse a name as vec, so the obfuscation makes it sound less like "vector" and is good. "Option" otoh is a great name
1 reply 0 retweets 3 likes -
THANK you
1 reply 0 retweets 1 like -
You're welcome
1 reply 0 retweets 0 likes -
"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
1 reply 0 retweets 5 likes -
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 @mgattozzi and
Speaking just for myself, I see Array as a group of elements and Buffer as a resizeable block, so the combination works at least for me as "resizeable group of elements"
1 reply 0 retweets 0 likes -
Replying to @myrrlyn @mgattozzi and
yes. My problem with "array" is that the english word invokes the image of a 2D array. My problem with "buffer" is that it's the least useful bit of info about the vec; most collections use buffers.
3 replies 0 retweets 1 like -
Replying to @ManishEarth @myrrlyn and
I actually like "list". However C++ ruined us by calling their linked list a list so there are problems there too.
3 replies 0 retweets 2 likes
Replying to @ManishEarth @myrrlyn and
Jinx
8:01 PM - 13 Dec 2017
from Albuquerque, NM
0 replies
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.