475da72c61
Turns out I've been including some unnecessary files when building apps/mu! Treeshaken stats before: LoC 26258 => 9717 LoC including common libraries: 29736 => 12719 binary size: 406K => 79K After: LoC 26258 => 9717 LoC including common libraries: 28322 => 12370 binary size: 406K => 77K So our treeshaking isn't perfect. No surprise there.. The treeshaken build also starts to fail without the one-liner change to mu.subx, which looks like a bug in the treeshaker.
17 lines
904 B
Plaintext
17 lines
904 B
Plaintext
Layers in the 3xx series use all the available syntax sugar for SubX programs.
|
|
Functions here can be called from Mu programs if they meet certain criteria:
|
|
|
|
- There's a signature for them in 400.mu
|
|
- Inouts on the stack, outputs in registers
|
|
- Valid Mu types everywhere (Mu's type system isn't expressive enough for
|
|
everything SubX does in rare situations.)
|
|
- No way to for an `addr` to escape a function. No `(... addr ... addr ...)`
|
|
inouts, and no `(... addr ...)` outputs.
|
|
|
|
While functions _can_ be called, not all SubX functions meeting these criteria
|
|
_should_ be called. In particular, avoid exporting functions that could be
|
|
misused. A classic example is trying to add a `size-of` operator. If you're
|
|
doing that you're likely going to rely on programmers to use it correctly. Mu
|
|
tries to be idiot-proof. Even if SubX requires greater care, using SubX
|
|
primitives from Mu should not.
|