Skip to content

! meaning compatability updated #1657

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

! meaning compatability updated #1657

wants to merge 2 commits into from

Conversation

twof
Copy link
Contributor

@twof twof commented Feb 17, 2025

In option 3, the meaning and mechanics of a ! adorned type change when a document adopts semantic nullability

@benjie
Copy link
Member

benjie commented Feb 17, 2025

Criteria C has been clarified in #1659 to only relate to the unadorned type; if you wish to add that ! should only mean strictly non-nullable in all modes then you should do so with a new criteria.

Comment on lines +500 to +501
- 🚫 `Int` reatains its meaning across both modes, but `Int!` means
non-nullable in one mode, but semantic non-nullable in another. Only
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"modes" here was referring to null bubbling enabled/disabled, and Int! always means semantic non-null when null bubbling is disabled, so all solutions would fail this criteria the same. As such, the commentary around Int! meaning has been removed from the criteria.

@benjie benjie closed this Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants