RFC for mandatory end designators #178
Open
Conversation
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
joaopsazevedo
force-pushed
the
mr/mandatory_end_designators
branch
from
5f24e14 to
63c082a
Compare
ronan-d
reviewed
Nov 18, 2025
| type My_Record is record | ||
| Foo : Unbounded_String; | ||
| Bar : Natural; | ||
| end My_Record; |
Contributor
There was a problem hiding this comment.
I think it should be end record; here.
sttaft
reviewed
Nov 18, 2025
| Open questions | ||
| ============== | ||
|
|
||
| None at this stage. |
Contributor
There was a problem hiding this comment.
You did not mention the alternative of making this a self-imposed Restriction rather than a massive incompatibility. You could allow the alternative syntax for ending a record, and then define a Restriction that would mandate it for a given project.
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.
For #177