Releases: miking-lang/miking-sublime-text
Releases · miking-lang/miking-sublime-text
Utest-else syntax support
Release Notes
- Support for
utest <expr> with <expr> using <expr> else <expr>
syntax - Fix issue with units and empty sequences that spans multiple lines
Typed MLang semantics
Release Notes
- Support for typed MLang semantics
- Identifier lookups for recursive lets
Variable lookup support and singleton tuple matching
Release Notes
- Support for looking up definitions by hovering over identifiers.
- Support for singleton tuple matching syntax.
Fix floating point parsing
Release Notes
- Floating point numbers now handles multiple digits prior to the dot and absent digits after the dot.
Support for new syntactic sugar, new expressions, and changes in type naming
Pre-release
Release Notes
- Support for
match <expr> with <pat> in <expr>
. - Support for
switch <mexpr> [case <pat> then <mexpr>]* end
external
supportlam.
(empty lambda) supportTensor [<ty>]
support- Support for mexpr sequence (
<mexpr> ; <mexpr>
) - MLang
type
aliasing support never
as part of an mexpr instead of a builtin identifierall <ident>
type support#frozen
identifier support
Type application - Block comments - (and minor fixes)
Release notes
- Support for type application
- Support for nested block comments
- Remove support for C++ style line comments
- Minor bug fixes.
Top-level utests and documentation
Release notes
- Adds top-level utests
- More documentation
- Better error-highlighting for reserved keywords
Reworked Syntax Highlighter - Reflect MCore Parser
Reworked the syntax highlighter to reflect the current state of the MCore parser. The highlighter is now concious about when it is scanning top-level expressions and when it is scanning pure mexpr-expressions.
Reworked the entire highlighter to be based on a modular system with fragments, to reduce the amount of code duplication needed.
Initial release
Provides an unfinished version of the syntax highlighter that is better than nothing. It currently lacks proper support for MLang where the top-level is yet to be implemented. This can lead to some incorrect highlighting in certain places, but mostly it works fine.