Custom Auto Traits

[TheNappap]

@Ixrec

That aside, what is the reason you don't want any larger types in this function? I can easily imagine reasons to put size assertions or size-checking unit tests within your own codebase (and that's already commonplace in some projects like servo), but for a public API I'm not aware of any use cases, since there are no operations you can perform on sizeN types that you can't also perform on sizeN+1 types.

I'm trying to create a Box-like structure based on the fixed sized traits idea:

Idea: Fixed sized traits

This is an idea I've been thinking about for some time now and I thought I'd share it. This is my first post here, so I hope I'm doing it right. Idea In short, the idea would be to have traits which impose a fixed size on its implementors. For example, by having a special `Fixed` trait. Consequences of this would be: default Sized trait objects, no need for indirection, matching on trait objects,... Traits and Enums I got this idea by looking into subtype/inclusion polymorphism i…

When creating such a trait object the size of the value can't be bigger than the size of the fixed sized trait.