HEL/midas
1
0
Fork 0
Code Issues Pull Requests Actions Releases 2 Activity

docs: fix some typos in manual

Browse Source
This commit is contained in:
Louis Heredero
2026-07-09 15:59:29 +02:00
parent 21b648e18f
commit cd9b80d22b
3 changed files with 847 additions and 809 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1651
docs/manual.pdf
View File

File diff suppressed because it is too large Load Diff

4
docs/manual.typ
View File

@@ -624,7 +624,7 @@ For example:
== Control flow
Some control flow features are supported. For the limited code of this project, not all constructs are supported. The following are those currently handled and typ checked by Midas.
Some control flow features are supported. For the limited code of this project, not all constructs are supported. The following are those currently handled and type checked by Midas.
=== `if` / `elif` / `else` <if-else>
@@ -757,7 +757,7 @@ If the value passed to `cast` or `unsafe_cast` is a literal (e.g. an integer, a
Vanilla Python already lets you use type hints to specify the type of variables and function parameters.
Midas use them to type check your code. Additionally, it allows you to use a special syntax to define a `Frame` types directly in these annotations.
Midas use them to type check your code. Additionally, it allows you to use a special syntax to define a `Frame` type directly in these annotations.
Because these annotations are not interpretable by Python, your integrated type checker might complain loudly about them being invalid.
A workaround is to silence it by adding a type comment at the end of the line, as shown in @silence-errors.

1
docs/template.typ
View File

@@ -61,6 +61,7 @@
set document(
title: title,
author: author,
date: none,
)
set text(
font: "Source Sans 3",