- Make section anchor unique, use characters not allowed in identifiers
- Make Record.hs like macro expansion more generic
- Use SyntaxError error type in Record.hs
- Special handling for
(define x (case-lambda …))
- Check for broken anchor links in generated HTML
- Consider removing declaration description
- Support
include-ci
inLibrary.hs
- Add flag to include un-exported identifiers in documentation
- Consider using
lucid2
instead ofblaze-html
- Ideally in combination with
mmark
- See: https://github.com/mmark-md/mmark
- Ideally in combination with
- Scribble-like syntax for comments
- Have a function call syntax e.g.
@function{parameter}@
- Map that to formatters to allow stuff like
@pre{code}@
- Should also allow for customizations through the SchemeDoc library
- Have a function call syntax e.g.
- Somehow allow for a semantic representation of scheme objects in the Formatable type class, e.g. don't already return specific heading levels etc
- Parser: Better error messages
- Tests: Perform some compliance tests of the R7RS parser
- Make it easier to use SchemeDoc as a library
- E.g. for supplying custom expression formatters