You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
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.
Three options:
It's a separate repo, which calls out to
bowtieto do everything. At the start all the tests pass, and over time the implementer replaces each call tobowtiewith their own implementation of evaluation, type inference, etc.It's a separate repo, with
undefinedfor each major function. At the start the tests fail, and go green as the user implements themIt's in the SAME repo (thanks @mitchellwrosen) for this idea. This way things like fuzzy file searching and
ghcidejump-to-definition still work. Perhaps it's in theKitnamespace instead ofBowtie.