Skip to content

How should the kit work? #4

@seagreen

Description

@seagreen

Three options:

  1. It's a separate repo, which calls out to bowtie to do everything. At the start all the tests pass, and over time the implementer replaces each call to bowtie with their own implementation of evaluation, type inference, etc.

  2. It's a separate repo, with undefined for each major function. At the start the tests fail, and go green as the user implements them

  3. It's in the SAME repo (thanks @mitchellwrosen) for this idea. This way things like fuzzy file searching and ghcide jump-to-definition still work. Perhaps it's in the Kit namespace instead of Bowtie.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions