Repository navigation
Fix: A companion module is callable when a factory shares its name (TextRange(2)) - #104
Merged
Merged
Conversation
…able module (SPEC U-8, B-7, #78)
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
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.
Closes #78
Defect fixed:
androidx.compose.ui.text.TextRangewas both the companion-constants child module (TextRange.Zero) and the factory overload set (TextRange__Int); the module won and was not callable. A name that is both is now a callable module (U-8); stubs declare it as a callable Protocol carrying the module's members (B-7).Verification (coordinator, after merging develop, separate modules): plugin 271/0, desktopTest 595/0, ksp artifact 35/0, app 70/0, compose 116/0, androidNative OK; regenerated Compose stubs pass tools/stubs/check-stubs.sh (mypy).