Skip to content

Type errors between operands #29

Description

@verdverm

What should we do when we encounter incompatible types while recursing in operators? Well, we should really let the user decide.

  • default is to ignore and treat in accordance with the operators default behavior
  • flags to control per run (see below)
  • attribute to determine on per node basis (@error())

do we need an ignore-type-errors to disable attributes? the current flags default to false, so we cannot use those. Do we want three analogous to the enabling type error flags?

  • enable/ignore
    • all
    • node
    • leaf

What other applications might an @error() attribute have?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions