Reflect the abstract type scenario more precisely in LRM#169
Merged
SurajBDeore merged 1 commit intomainfrom Mar 3, 2026
Merged
Reflect the abstract type scenario more precisely in LRM#169SurajBDeore merged 1 commit intomainfrom
SurajBDeore merged 1 commit intomainfrom
Conversation
4fac8fd to
263cce7
Compare
Scenarios to consider: 1. Abstract type without object and without extension: covered by linter, now also specified as implementation recommendation in the LRM. 2. Abstract type + extension: covered by LRM, neither warning nor error shall be emitted. 3. Abstract type + object: covered by LRM, error expected. LRM now reflects the above scenarios more precisely through an implementation recommendation. System tests and traces have been added.
263cce7 to
8bd8085
Compare
SurajBDeore
approved these changes
Mar 3, 2026
Contributor
SurajBDeore
left a comment
There was a problem hiding this comment.
Thank you for this change
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.
Scenarios to consider:
LRM now reflects the above scenarios more precisely through an implementation recommendation.
System tests and traces have been added.