Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deserialization of Components and Configuration #192

Open
Saethox opened this issue Aug 20, 2023 · 1 comment
Open

Deserialization of Components and Configuration #192

Saethox opened this issue Aug 20, 2023 · 1 comment
Labels
backlog This issue is postponed enhancement New feature or request

Comments

@Saethox
Copy link
Collaborator

Saethox commented Aug 20, 2023

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.

@Saethox Saethox added enhancement New feature or request backlog This issue is postponed labels Aug 20, 2023
@Saethox
Copy link
Collaborator Author

Saethox commented Aug 21, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog This issue is postponed enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant