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

Analyse if we could use code generation instead of reflection for serix #653

Open
muXxer opened this issue Jan 15, 2024 · 1 comment
Open
Labels
team-node Issues for Node Team
Milestone

Comments

@muXxer
Copy link
Collaborator

muXxer commented Jan 15, 2024

Right now, we use reflection during runtime to serialize objects in serix.
This affects the performance negatively and it's hard to check if we serialize all different types properly.

We should investigate if there is a way to use code generation instead.

@muXxer muXxer added this to iota-core Jan 15, 2024
@muXxer muXxer converted this from a draft issue Jan 15, 2024
@muXxer muXxer added the team-node Issues for Node Team label Jan 15, 2024
@muXxer muXxer added this to the v1.0.0-rc milestone Jan 15, 2024
@alexsporn
Copy link
Member

Also think about #497 when checking out code generation.

@alexsporn alexsporn moved this from Backlog to Product Backlog in iota-core Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-node Issues for Node Team
Projects
Status: Product Backlog
Development

No branches or pull requests

2 participants