Skip to content

Conversation

@yannl35133
Copy link

This fix is not subtle, there may be better ways to do this. As long as you stop relying on Type irrelevance, this will work

@yannl35133 yannl35133 force-pushed the stricter-type-in-type branch from 0f0a56f to 9749e00 Compare January 27, 2026 18:09
@yannl35133
Copy link
Author

@CohenCyril can you take a look? The use of Type-in-Type that is removed looks dubious, but I don't understand the proofs so I can't fix it.

@CohenCyril
Copy link
Member

Oh indeed this is suspicious...

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