Swap over to parser combinators for ease of syntax additions

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
compilers

Research direction

The issue body names no files, tests, or entry points. Start by locating the current syntax parser and its tests, then determine the parser-combinator design and confirm that existing lambda-calculus syntax and tests still work.

Written by the indexing model from the issue text.

Description

This issue has no description.

Dominant language
JavaScript
Stars
69
Forks
10
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 evinism/lambda-explorer

All issues in evinism/lambda-explorer

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.