State the effect wrapper declaration without a rank-1 special case - #141
Merged
Merged
Conversation
The checked scheme's binders stay on the wrapper's quantified list and the closure monotype stays in ty. That is the Core declaration shape for a quantified import and a monomorphic one. The 2026-10-04 board is unchanged at 124/413.
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
1 participant
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.
The effect-entry documentation on master already carries the contract from
docs/effect-command-contract:IntandEffect Unitentries, the lexicalrunEffectrule, and checked WIT schemes. This removes the later evidence sentences that described that wrapper as a rank-1 special case.The wrapper declaration keeps the scheme binders on
quantifiedand the closure monotype inty. The 2026-10-04 scoreboard stays 124/413.Refs #78