Skip to content
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.

Sign up for GitHub

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

Jump to bottom

compute effects of lambdas #294

Open
JonathanAldrich opened this issue Jan 17, 2019 · 1 comment
Open

compute effects of lambdas #294

JonathanAldrich opened this issue Jan 17, 2019 · 1 comment
Labels
bug

Comments

@JonathanAldrich
Copy link
Member

When a lambda is in a context where effect checking is enabled -- e.g. the lambda is within a file that is effect-checked (see issue #293) or it is within a function that is annotated with effects - then the lambda should be effect checked and an effect should be part of its type.

I'm marking this as a bug (not an enhancement) because there is no way to get effects checked on a lambda without this, and the effect system is unsound for lambdas without this.
@JonathanAldrich JonathanAldrich mentioned this issue Jan 17, 2019
Open
@JonathanAldrich
Copy link
Member Author

example: twice.wyv

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JonathanAldrich