Skip to content

Revisit how we determine operator type errors #173

@heshanpadmasiri

Description

@heshanpadmasiri

Currently we give some errors in type resolver and some in semantic analysis. Techically we can't actually give most of these errors until we have done conditional type narrowing. We do need the type of some expression to do conditional type narrowing but not binary expression. I think we need to refactor this such that we can avoid double checking these.

Metadata

Metadata

Assignees

No one assigned

    Labels

    FrontendChange is purely for front end no change to runtime is expected

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions