Conversation
added 2 commits
August 28, 2026 21:41
…ger initializes unvetted classes
|
Contributor
|
I do not believe that we need a new constant to allow arbitrary classes to be used as ObjectIdentity. |
Contributor
Author
|
I agree with Craig's commet. Altough it is a backward compatibility issue to remove support for arbitrary classes to be used as ObjectIdentity, I also think this is not a problem in practice. People will use classes like LongIdentity or StringIdentity or come up with their own ObjectId class and then there is no problem. |
This file contains hidden or 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
2 participants
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.
Identity-key construction gated on an allowlist; Class.forName no longer initializes unvetted classes