Skip to content

fix: no libraries in TL-B #1409

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 22, 2025
Merged

fix: no libraries in TL-B #1409

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0318230
fix: no libraries in TL-B
gabriel-fallen Nov 21, 2025
8af3ecd
fix: remove a blank line
gabriel-fallen Nov 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 0 additions & 26 deletions languages/tl-b/syntax-and-semantics.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,32 +79,6 @@ a comment
// This is a single-line comment
```

### Libraries import

You can use **TL-B libraries** to extend your documents and to avoid writing repetitive schemes.
In TL-B libraries, there is no concept of cyclic import.
Just indicate the dependency on some other document (library) at the top of the document with the keyword `dependson`:

```tlb
//
// dependson "libraries/tosstdlib.tlb"
//

op:uint32 data:Any = MsgBody;
something$0101 data:(Maybe ^MsgBody) = SomethingImportant;
```

In dependencies, you are required to specify the correct relative path. The example above is located in such a tree:

```
.
├── mydoc.tlb
├── libraries
│ ├── ...
│ └── tosstdlib.tlb
└── ...
```

## Semantics

From a high-level perspective, the **right-hand side** of each _scheme_ is a type, either simple (such as `Bit` or `True`) or parametrized (such as `Hashmap n X`) and
Expand Down