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
-
List really falls in like with the "what this thing does" of Map, Set, Tree. For a systems language you may want to also include impl details, so HashMap, HashSet, BTreeMap (oops, tree and map.).
Given this is a type that newcomers encounter very early and is much more fundamental, I dont think including implementation details in the name is terribly important
-
-
Right, but you might need to cater to both especially when there are multiple Lists. It's a hard problem.
-
Which is why Vec works out better in practice. Vec isn't too misleading.
- 1 more reply
New conversation -
-
-
Wait we're missing something null is None non-null is Some(T) group should be Many[T]
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.