v0.7.1

Changes

• Add missing to-char converter
• Move lostanza types to lostanza-only scope
• Add some special-case lostanza construct detections
• Support more new instantiated type signatures

v0.7.0

Changes

• Change some selectors to match themes better
• Move all to-* functions to separate selector for more emphasis
• Add block-scoped lostanza highlighting
• Add block-scoped this highlighting (inside new blocks)
• Move deref/tuple highlight to main grammar (considering making this only work on % or inside lostanza liberally)

v0.6.0

Changes

• Properly capture parameterized types
• Allow types to be followed by = (variable/value declarations)
• Change do to control keyword style highlighting
• Remove all type/ref/ptr parameter highlighting (looks cleaner)
• Fix _ inside identifiers inside anonymous functions
• Add here-string support e.g., \<some-tag>some text here<some-tag>

v0.4.0

Changes

• Add s-expression literals
• Fix for brackets preceded by opening parenthesis

v0.3.0

Changes

• Added lostanza keywords
• Special highlighting of ptr/ref parameters
• Allow support functions to highlight when followed by $
• Tweak char strings
• Tweak support functions
• Fix type highlighting (and add -)
• Fix inheritance not closing

Drawbacks

I had wanted to only highlight lostanza things inside lostanza blocks but no matter what I tried, nothing seemed to work. It would have to follow these rules:

1. Contain all connected lines at that level of indentation
2. Would also include any blank lines (most editors trim off the whitespace of blank lines)
3. Would also include deeper indentation
4. Would only end when a line with text is initiated at a lower level of indentation (or the end of the file)

Getting all four was challenging. If I left out 2, this problem wouldn't be that bad because you could just stop at the next blank line but I see that as an unacceptable limitation to bake into a syntax highlighter. That being said, I am totally willing to accept any PRs that solve this!