You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While Configurations are already serializable, the state of deserialization currently looks pretty dire. While some work on de(serialization) of boxed trait objects exists with typetag, it currently does not support trait objects with generic parameters (like Component<P>), and I believe also not generic impls of the trait (e.g. implementing Component for a component with an identifier I).
In general, it would be very nice to deserialize Configurations, especially if they were dynamically created.
The text was updated successfully, but these errors were encountered:
While the issue with deserializing Component<P> could probably be solved by an own Deserialize<P> trait, I'm really not sure how to deserialize structs with generic parameters into boxed trait objects.
While
Configuration
s are already serializable, the state of deserialization currently looks pretty dire. While some work on de(serialization) of boxed trait objects exists withtypetag
, it currently does not support trait objects with generic parameters (likeComponent<P>
), and I believe also not generic impls of the trait (e.g. implementingComponent
for a component with an identifierI
).In general, it would be very nice to deserialize
Configuration
s, especially if they were dynamically created.The text was updated successfully, but these errors were encountered: