tlang
/
documentation
mirror of https://github.com/tbklang/documentation
1
0
Fork 0
Code Issues 3 Packages Projects 2 Releases Activity

TypeChecking 

- Remoevd now-completed TODO
- Typo fix
This commit is contained in:
Tristan B. Velloza Kildaire 2023-07-09 14:57:01 +02:00
parent e690dc9619
commit 2a83a653d5
1 changed files with 1 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs_src/implementation/35-typechecking.md
View File

@ -238,8 +238,6 @@ TODO: Document this now
Coercion has a set of rules (TODO: docuemnt them) in terms of what can be coerced. AT the end of the day if the coercion fails then a `CoercionException` is thrown, if, however it succeeds then a `CastedValueInstruction` will be placed into the memory location (the variable) pointed to by the `ref` parameter of `typeEnforce(..., ..., ref Instruction coercedInstruction, true)`.
TODO: Document the usage of this for variable assignments for example
##### Example
Below we have an example of the code which processes variable declarations _with assignments_ (think of `byte i = 2`):
@ -278,7 +276,7 @@ What the above code is doing is:
* The third argument, is `ref`-based, meaning what we provide it is the variable which will have the result of the enforcement (if coercion is required) placed into
* The last argument is `true`, meaning _"Please attemt coercion if the types are not exactly equal, please"_
The last line ocnatining an asssertion:
The last line containing an asssertion:
```{.d .numberLines}
assert(isSameType(