Skip to content
This repository was archived by the owner on Apr 1, 2025. It is now read-only.
This repository was archived by the owner on Apr 1, 2025. It is now read-only.

Precise AST datatypes’ fields are generated in arbitrary order #483

@patrickt

Description

@patrickt

Ported from tree-sitter/haskell-tree-sitter#97.

They don’t reflect either the node-types.json file’s declared order or order within the grammar. This is due to aeson using HashMaps to represent objects during JSON parsing, which means that we get keys back in hash order.

Metadata

Metadata

Assignees

No one assigned

    Labels

    ast:codegenBugs in Template Haskell AST generation

    Type

    No type
    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