1. Introduction
  3. Editor Integration
  4. Common Configurations
  5. 1. Editor Frontends
    1. 1.1. VS Cod(e,ium)
    2. 1.2. Neovim
    3. 1.3. Emacs
    4. 1.4. Sublime Text
    5. 1.5. Helix
    6. 1.6. Zed
  8. Features
  9. 2. Command line interface
  10. 3. Code Documentation
  11. 4. Code Completion
  12. 5. Exporting Documents
  13. 6. Document Preview
  14. 7. Testing
  15. 8. Linting
  16. 9. Other Features
  18. Service Overview
  19. Overview of Service
  20. 10. Principles
  21. 11. Commands System
  22. 12. LSP Inputs
  23. 13. Type System
  25. Service Development
  26. 14. Crate Docs
  27. 15. LSP and CLI
  28. 16. Language Queries
  29. 17. Document Preview

Tinymist Docs

The underlying techniques are not easy to understand, but there are some links:

  • bidirectional type checking: https://jaked.org/blog/2021-09-15-Reconstructing-TypeScript-part-1
  • type system borrowed here: https://github.com/hkust-taco/mlscript

Some tricks are taken for help reducing the complexity of code:

First, the array literals are identified as tuple type, that each cell of the array has type individually.

Second, the and the type are reused frequently.

  • the type is notated as , and the type is a special tuple type .

  • the type is imported from mlscript, notated as .

  • the type consists of:

    • a positional argument list, in type.
    • a named argument list, in type.
    • an optional rest argument, in type.
    • an optional body, in any type.

    notated as

  • the is a without rest and body.

With aboving constructors, we soonly get typst's type checker.

  • it checks array or dictionary literals by converting them with a corresponding and .
  • it performs the getting element operation by calls a corresponding .
  • the closure is converted into a typed lambda, in type.
  • the pattern destructing are converted to array and dictionary constrains.