-
Notifications
You must be signed in to change notification settings - Fork 102
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
Fix TC allowing bad schemas in bind, with-read, with-capability #1212
Fix TC allowing bad schemas in bind, with-read, with-capability #1212
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great to me, I'll kick off a replay now.
This only affects static typechecker so no replay is necessary |
Thanks, @sirlensalot, that should have been obvious to me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thanks @sirlensalot 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great catch! fyi I've verified that my return-types PR now passes tests when rebased on this. (although that's not surprising, because PR-1212 fixes the Pact code that didn't typecheck before).
Replay doesn't need to be involved for PR-1212, but are there any other backward compat issues we need to think about? (e.g. a customer that runs TC and accidentally relied on the previous lax TC behavior?)
In general breaking repl-only compat is ok, and static TC + FV are even more so as they're supposed to be about correctness first. Finally since this goes with the runtime TC fork that certainly trumps repl compat. |
No description provided.