|
|
Log in / Subscribe / Register

Shared libraries

Shared libraries

Posted Dec 1, 2025 23:30 UTC (Mon) by NYKevin (subscriber, #129325)
In reply to: Shared libraries by ballombe
Parent article: APT Rust requirement raises questions

There is not. You would need to remove or severely restrict all of the following:

* References (lifetimes are considered type parameters), but maybe we can make an exception since lifetime parameters do not result in true monomorphization.
* Slices and arrays (the element is considered a type parameter, and gives rise to monomorphization in the usual fashion).
* Async (Future<T>)
* for loops and iteration (Iterator<T>)
* Smart pointers (Deref<T>)
* Result<V, E> and Option<T>, and all APIs that return things in one of those two forms (i.e. every fallible function in std and core). That includes basically all I/O.

And probably a dozen other things I didn't think of. Needless to say, the resulting language would be so constrained as to make WUFFS look like a "normal" language in comparison.


to post comments


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds