Backlog

[plexus]

• Syntax features
  • regular expressions
  • hexadecimals (0x...)
  • namespaced maps
  • metadata
  • #=(...)
  • #?() / #?@()
  • quote / backquote / unquote / splice
  • 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
  • propagate lex errors when :fail-fast

[volrath]

@plexus what about adding a zipper and utility funcs for AST traversal? or do you feel it'd be out of this project scope?

[plexus]

I'd be interested to see AST zippers. I do feel most of the above is more essential though.

[volrath]

@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.