Remove the need for `Selector`

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
haskell
Domain
compilers

Research direction

Start by tracing the Let statements that still use the old abstract mechanism and compare them with the framework in Brat.Checker.SolvePatterns. Done means Let statements use the new pattern-matching framework, and the abstract mechanism and Selector nodes are no longer generated or compiled.

Written by the indexing model from the issue text.

Description

We still have code (Let statements specifically) which use the old abstract mechanism instead of using the framework in Brat.Checker.SolvePatterns. This is the only thing that generates Selector nodes, which we don't compile.

Everything should use the new pattern matching framework, and we should get rid of abstract and Selector

Dominant language
Haskell
Stars
8
Forks
1
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Quantinuum/brat

All issues in Quantinuum/brat

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.