Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

move to more performant internal representation

Open
#7 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
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
compilers

Research direction

Start by locating the current expression representation and the beta-reduction entry point in the JavaScript project. Add tests for the proposed composed representation and measure whether large functions improve, while treating compilation before beta reduction as a separate design question.

Written by the indexing model from the issue text.

Description

performance

The current internal representation leaves a lot to be desired.

Low hanging fruit would be to directly represent a(a(a(a(b)))) not as 5 different functions, but maybe just one function with a composed: 4 key. That would probably make performance actually acceptable for large functions.

The final version of this is that we can probably get hella hella speed improvements if we 'compile' the expression before beta reduction... but that sounds hard.

Requires having tests

Dominant language
JavaScript
Stars
69
Forks
10
PR merge metrics
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.