Allow private constructors when using ctor attribute #530
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The idea here is that adding
SerializationConstructorattribute to a constructor is such an explicit action/flag, that it should override any priv/nonpriv solver constraint. I would argue that the same should be the case forKeyattribute and similar as well, because adding[Key(0)]to something and having it ignored because it's private is confusing. But regardless, that you can at least work around. Private constructors don't work at all as is.I would also really like a
[MessagePackObject(IgnoreByDefault = true)], so I don't have to keep doing[IgnoreMember]on all the public API. Thoughts?Closes #40