Skip to content

Properly evaluate constants that depend on other constants #57

Description

@mrwright

Right now, constants are evaluated in an arbitrary order. If a constant refers to another that hadn't yet been evaluated, the compiler will give an error.

It looks like there's already a framework for toposorting consts, but it's not yet used.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions