Skip to content

compute effects of lambdas #294

Open
@JonathanAldrich

Description

@JonathanAldrich

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions