Skip to content

report when we try to convert a mutually-recursive top-level definition #44

Open
@zliu41

Description

@zliu41

Right now categorize simply gets stuck in a loop when we try to categorize a mutually-recursive function.

I think the problem is tied to inlining, so it would be great if we could keep track of what we've inlined, and error if we try to inline a function that we're in the middle of converting already.

The problem with this approach currently is that we usually inline the original expression within a larger unconverted expression, then convert the larger expression, so it's possible that if we just track it in the larger expression that we're noticing parallel invocations of the same function, rather than nested ones.

Perhaps we could manually introduce a Tick node whenever we inline, so then we can notice that we hit the inlined identifier within the larger expression.

(Extricated from https://kitty-hawk.atlassian.net/browse/SW-2733)

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