mType 1.0.0 Known Limitations

The 1.0.0 release is a stable-core release. The following advanced gaps are documented follow-up work and do not block the release.

Language Server

Range formatting is not implemented. The server advertises full-document formatting only.
Some diagnostics and quick fixes are intentionally conservative when workspace indexing is still warming up.

Nested classes and nested interfaces are rejected.
Some generic cast cases remain conservative, especially where runtime generic type identity cannot be proven precisely.
Generic isClassOf-style runtime type checks are intentionally limited in nested generic cases.

JIT specialization is limited to proven hot paths and may fall back to VM execution for unsupported operations.
Some multi-dimensional array and structure-of-arrays optimizations are intentionally conservative.
Shape-specialized generics have eligibility limits, including user-defined equality/hash behavior and inline-slot budgets.
Depth-2 OSR inlining can hang on certain stream pipelines (MYT-254). When both an outer count()-style loop and an inner iterator's advance() loop both become hot enough to OSR-compile (roughly when the inner sequence has ~6 or more elements), the depth-2 inlined view of hasNextElement can be read as permanently true and the pipeline never terminates. Function-level JIT and depth-1 inlining are unaffected. Workaround: build with INLINE_DEPTH_LIMIT lowered to 0 or 1 in mType/vm/optimization/InlineAnalysis.hpp to disable depth-2 nested inlining. A proper fix to OSR codegen / re-entry is tracked under MYT-254.

GitHub Releases are the only 1.0.0 distribution channel.
Marketplace publishing, MSI, Homebrew, apt, winget, Chocolatey, and Scoop packages are out of scope.