evinism / evinism/lambda-explorer

move to more performant internal representation

Aperta
#7 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
performance
Lingua principale
JavaScript
Stelle
69
Fork
10
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

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

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.