Skip to content

Loop detection could be done in message/term reference instead of pattern (?) #277

@Pike

Description

@Pike

When looking at @spookylukey's evaluator, I noticed that the dirty-handling is done in pattern.

That's on a pretty hot code path.

Could we do that in message reference and term reference instead?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions