"Do you have details on that? I'd..." <- > <@jordens:matrix.org> Do you have details on that? I'd love to understand that. > I know how trait objects work and how they are implemented but have a hard time imagining why it should be "terrible". From what I've seen when experimenting with casts and trait objects on embedded (in `crosstrait`, `serde-erased` etc) it looked just fine. > The one bloat case I can see now is trait objects preventing inlining of monomorphizations. I'm kind of curious why there is such a fear of `dyn` in embedded. The hacky C equivalent (structs of function pointers) is really common in most RTOSes. Performance wise, the main cost is a lack of inlining, but otherwise, jumping through function pointers isn't that expensive.