Skip to content

Conversation

@capfredf
Copy link
Member

When using an expected arrow type to check a lambda with not every parameter
annotated, the existing annotation was thrown away, and the lambda was treated
as non-annotated one.

closes #1011

@capfredf capfredf force-pushed the fix-1011 branch 3 times, most recently from 15b1db4 to b8c9cf1 Compare January 16, 2021 14:32
@capfredf
Copy link
Member Author

capfredf commented Jan 16, 2021

blocked by #1020

@capfredf capfredf force-pushed the fix-1011 branch 3 times, most recently from d1dcdca to cf74141 Compare January 20, 2021 02:27
When using an expected arrow type to check a lambda with not every parameter
annotated, the existing annotation was thrown away, and the lambda was treated
as non-annotated one.

closes racket#1011
@capfredf capfredf merged commit 5b502e7 into racket:master Jan 20, 2021
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.

fails to catch ill-typed property values that are partially annotated

2 participants