Skip to content

Require matching finality - #112

Merged
tlively merged 1 commit into
mainfrom
require-matching-final
Sep 4, 2026
Merged

Require matching finality#112
tlively merged 1 commit into
mainfrom
require-matching-final

Conversation

@tlively

@tlively tlively commented Sep 1, 2026

Copy link
Copy Markdown
Member

Rule out the nonsensical configurations in which finalities of descriptor and described types are mismatched. In these configurations, it would not be possible for the non-final type to have subtypes, so we might as well require it to be final.

Closes #61.

Rule out the nonsensical configurations in which finalities of descriptor and described types are mismatched. In these configurations, it would not be possible for the non-final type to have subtypes, so we might as well require it to be final.

Closes #61.
@tlively

tlively commented Sep 1, 2026

Copy link
Copy Markdown
Member Author

@rossberg, do the CI failures setting up OCaml look familiar to you? Is that something that a merge from the upstream spec would fix?

@rossberg rossberg left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks good.

Re CI failures: not sure. But dependency handling has been cleaned up upstream (plus it moved to OCaml 5). So if rerunning the job does not fix it, perhaps consider syncing with upstream.

@tlively
tlively merged commit e9f7a93 into main Sep 4, 2026
1 check failed
@tlively
tlively deleted the require-matching-final branch September 4, 2026 19:13
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.

Requiring descriptors to have matching finality

2 participants