parseclj
parseclj copied to clipboard
Backlog
- Syntax features
- [x] regular expressions
- [x] hexadecimals (0x...)
- [x] namespaced maps
- [x] metadata
- [x] #=(...)
- [x] #?() / #?@()
- [x] quote / backquote / unquote / splice
- [x] var literal #'
- parseedn
- [ ] lossless output format
- [ ] unify string/buffer usage (optional first string arg)
- [ ] raise errors on non-EDN syntax
- parseclj-ast
- [ ] implement parseclj-ast-value
- [ ] zippers / AST traversal helpers
- General
- [ ] Add more docstrings
- [x] propagate lex errors when :fail-fast
@plexus what about adding a zipper and utility funcs for AST traversal? or do you feel it'd be out of this project scope?
I'd be interested to see AST zippers. I do feel most of the above is more essential though.
@plexus Right. I wasn't trying to make any statement on priorities, just wondering about the fact that this should be included into the backlog.
By the way, what do you mean about "implement parseclj-ast-value"? Is that a selector that will return the value of a node as an elisp data structure, or as a AST (node) data structure?
I think I could start by making the project a bit more MELPA-compliant in a few days. I'll let you know.