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

Allow SerializerStates and Writers to own their SerializerConfigs #20

Merged
merged 1 commit into from
Jul 7, 2024

Conversation

Ten0
Copy link
Owner

@Ten0 Ten0 commented Jun 18, 2024

Resolves #14

This makes them easier to manage (no need for self-referencing) when they are seldom instantiated but need to be moved around/stored...

This makes them easier to manage (no need for self-referencing) when they are seldom instantiated but need to be moved around/stored...
@Ten0
Copy link
Owner Author

Ten0 commented Jul 5, 2024

The reason I haven't merged this yet is that it shows regressions in the benchmarks and at this point I'm still unsure whether that's just noise.

@Ten0
Copy link
Owner Author

Ten0 commented Jul 7, 2024

Ok so I've run more benchmarks so I'm convinced now that this is absolutely just noise.

@Ten0 Ten0 merged commit 5ecd1ab into master Jul 7, 2024
4 checks passed
@Ten0 Ten0 deleted the owned_config branch July 7, 2024 13:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

I would love a way to create a Writer without mutable borrow of SerializerConfig
1 participant