04. Where does this file even go?
Module layout, compilation units, visibility, and how corelib fits on disk.
Where does this file even go?
You have a project. Now you have forty .bd files and no idea which folder earns the right to be called internal.
Beskid uses a file-backed module model: one file, one module, dotted paths map to directories. No secret module graph maintained by reflection and prayers.
What you will find here
Section titled “What you will find here”| Section | Topic |
|---|---|
| Module layout | Folders, file-scoped mod, flat vs nested. |
| Compilation units | What the compiler sees per file/target. |
| Visibility basics | pub, boundaries, leaking helpers. |
| Corelib layout | Standard library packages and corelib identity. |