psiayn/spressolisp

lisp in rust

spressolisp's Issues

Support for Unit Type

Examples

Various examples that demo language features

Macros and Metaprogramming

All the jedi powers

Fix formatting and add `cargo fmt` to CI

Some of the code isn't formatted. Can be fixed by running cargo fmt.

We should also enforce formatting by checking for formatting in CI. See this for an example.

Cache in CI

CI takes around 2 mins to build and test - most of which is downloading and building dependencies. This can be cached.

See mobusoperandi/michie#52 for an example on how to add cache to CI for a rust project.

tutor baked into repl

Vimtutor but much smaller baked into the repl.

Support for recursion

Aesthetics

Adding aesthetics to the repl such as

• bracket matching
• syntax highlighting
• autocomplete

Editor support

Start with at least

• emacs
• nvim

More functional programming

Reduce, filters, further testing of map and other functions.

Disallow expressions without parens

Something like this is heresy against lisp (shows current behaviour):

spresso> print
built-in function
spresso> print "hello"
"hello"
spresso> + 10 20
20
spresso> define x 10
Runtime Error: Symbol not found: x
In input[3]:
1   | define x 10
             ^

spresso>

Disallow expression that starts with a non-callable

Example:

spresso> (1 2 3 4)
1

This just returns the value of the first expression (1) and ignores the rest. It's not good to implicitly ignore expressions. An error should be raised indicating that 1 is not something that can be executed. This syntax should only work for functions and lambdas that can be executed with some args.

remove quotes in string while printing a string

When executing (print "Hello, World!"), the output is "Hello, World!", instead it's better to have Hello, World!.
But then if we are printing a list containing a string or likewise, we want to print quotes to clearly show it's a string.

One idea could be could be to handle a single Atom::String separately.

Use clippy to fix code issues and add it to CI

cargo clippy currently emits nearly 50 warnings (and 1 error) on the current code base.

Tasks:

• Run cargo clippy --all-targets --all-features and fix all code improvements suggested by it.
• Add cargo clippy --all-targets --all-features -- -D warnings as a step to CI (after build, test, fmt, etc.) to ensure we have always have a codebase that satisfies clippy. The command was suggested here