I'm reviewing a PR for a derive macro which can handle both structs and enums.
The code uses the name "Container" to mean "either a struct or enum". To me that name feels a bit awry because I think of container to be synonymous with "collection" (e.g. Vec).
This.
The only thing I have to add to that is that you can also sort-of create types with type MyResult<T> = std::result::Result<T, MyError> though technically that's defining a new alias for a pre-existing type.