fix: snapshot workfactor on credential creation #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
This change addresses an issue where modifying the
Config.WorkFactorafter creating a credential could inadvertently affect existing credentials because they shared the sameWorkFactorpointer.Changes
The fix introduces a
cloneWorkFactorhelper that performs a shallow copy of theWorkFactorstruct using a type switch (avoiding reflection and marshal overhead). It also updatesConfig.NewCredentialto store an independent copy in theCredential.Testing
All tests (including linters) pass. Benchmark shows a slight difference in allocations, which is understandable:
Backwards compatibility
No API changes.