feersum
feersum copied to clipboard
A Scheme compiler that targets .NET written in F#
Bringing the new parser up to speed. Replacing all uses of the old parser with the new one, and binning the old parser. TODO: * [x] Compiler * [ ]...
Current environment slot naming is of the form `_env_0` where 0 is the slot index. It would be nice if this better represented the value that is to be stored...
It would be nice to generate .xml style docs for our libraries. An example format for these comments in Scheme is SchemeDoc: http://people.cs.aau.dk/~normark/schemedoc/ see also monodocer: https://www.mono-project.com/docs/tools+libraries/tools/monodoc/generating-documentation/
Currently dotted pairs are quoted as a list conianing the dot as an identifier. It seems like Scheme expectes them to be quoted as a pair instead. It could be...
Only make instance methods on the environment iff the parent is captured. The current emit context keeps track of the parent context to handle the case where the _current_ method...
Scheme has the idea of a heirachical tower of numbers. Currently we only support `double` to represent Scheme's _real_ numbers. This is standards-compliant but a bit underwhelming. We should expand...
At some point it would be nice to support optimisations. I think that some form of gradual typing / type inference would help here. For _many_ scheme expressions the latent...
The current `syntax-rules` implementation generally _works_, but leaves a little to be desired. Namely: * [ ] No support for quoting of the ellipsis character `(... ...)` * [ ]...
Our current debugger support is a bit rough around the edges. * [x] Bound tree contains sequence points for debuging * [ ] Debuggable REPL. Embedded source in PDBs? *...
Our current REPL leaves a little to be desired. It would be nice if we had a better embeddable scripting API in the compiler so state could be carried across...