I don’t know if it will be useful anywhere except Tria 
Ahhh, yes, that’s true and I came up with several solutions and chose the solution with separating code into contexts.
Modules will be divided into groups, and each module group will be joined and compiled into separate module. Inlinings between groups won’t be possible.
So, the problem is to divide modules into groups. Right now Tria compiles everything into one group (called TriaGlobalContext) And my ideas for this are
- Using @sasajuric 's
Boundary - Using explicit tria annotation
- Profiling application during testing and using this data to statistically find optimal groups
- Just compiling everything into one module
