One fun side effect of lisp-style syntax: there's always a close token that corresponds to each expression. You can hover unambiguously.
(This tiny web page is at https://pl-toys.surge.sh/ if you want to play with it.)
miniblog.
Related Posts
The literal 0xffu8 in Rust is pretty tricky to read without syntax highlighting. It looks like a plain hexadecimal value at first.
(Why not have syntax highlighting? Ironically I was debugging and improving VS Code's Rust highlighting.)
I'm looking at adding bitwise AND and OR to my programming language. Do I add & and | operators, methods x.and(y) or a library bitwise::and(x, y)?
My inclination is to add infix operators (concise and familiar) but syntax is such precious real estate.
I've been iterating further on how Garden shows type errors.
For types in the standard library, I'm now showing "a String" but "an Int". I'm also doing basic syntax highlighting of the code excerpt.
What do you think?