Closed ExpHP closed 3 years ago
According to the Rust API Guidelines on naming I think Hlist!
is right.
It's like our HList
trait, which is named like BTreeMap
Yeah true; according to the API guidelines BTree
should be Btree
; this might have been before the API guidelines time?
I consider the B to be a separate word. Notice that somebody else found it necessary to use b_tree_map
as an antiexample in the guidelines, presumably because they perceive it as a separate word too
To be honest I often get it wrong myself when using the type macro so I'm open to re-naming it. Asides from naming convention, I think I may have wanted to avoid ambiguity between the type macro and the HList
trait
Since we're talking breaking changes, I'd like to throw this out there:
I mistype
Hlist!
asHList!
almost every time I use it. Why is it named this way, and how do others feel about this?