This repository was archived by the owner on Apr 7, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 141
fix: fixed visibility of LazyInit methods #461
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's probably too late to make this change without a major version bump.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that it would normally require a major version bump to make such a change. I would however argue that in this specific case we should consider relaxing that requirement for the following reasons:
get()method as package-private, which means that the class can currently only be (purposefully) used by the client library itself, as any outside user would not be able to get an instance of the object that is created.initialize()method would break any application that is directly calling the method, but that is not the intention of the method (and would also make no sense).initialize()method does not break any application that extends the class and overrides this method using public visibility, as increasing the visibility of an overridden method is allowed.So I would say that the probability of this change actually breaking source compatibility with any users is negligent. The change obviously does break binary compatibility.
All that being said: I would rather drop this specific visibility change than do a major version bump just for this. So if my arguments are not convincing enough (which I can perfectly understand from an API maintenance perspective), I'll revert this part of the change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The get method change is fine. As you point out, it's OK to increase visibility. If that's sent separately, I'm fine with that much.