evinism / evinism/lambda-explorer

move to more performant internal representation

Open
#7 0 comments 0 reactions 0 assignees View on GitHub
performance
Dominant language
JavaScript
Stars
69
Forks
10
PR merge metrics
No merged PRs in 30d

Description

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

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.