portability-wg
portability-wg copied to clipboard
rust-lang-nursery
Coordination repository of the portability Working Group (WG)
Often, global decisions affecting the entire dependency tree need to be made. Current examples of this in `std` are panic behavior and the global allocator. Outside of `std` there are...
Currently, `std` contains platform-specific code throughout. This makes both in-tree and out-of-tree ports harder. In-tree ports are harder because it's not obvious what all needs to be implemented. Out-of-tree ports...
As far as I understand, the `sys_common` module is meant to be common to all platforms. However, `sys_common::net` assumes existence of a LibC, specifically for some of its types: ```...
"it needs to disappear" from the perspective of the user. Quoting @japaric https://github.com/rust-lang-nursery/embedded-wg/issues/64 > In no_std programs you have to explicitly link to the compiler_builtins crate or at least one...
Lots of issues touch both WebAssembly and general portability. Reference this issue in the WebAssembly WG issue tracker to create a link to the portability WG.
A lot of existing crates “just work” when using them on another platform or in another environment. Others require minor changes. How does one find such crates? Alternatively, given a...
@Ericson2314 do you want to write the text for this one? ------ @Ericson2314 taking a stab at it per @jethrogb's request: Much the various abstractions in `std` require different implementations...
Lots of issues touch both embedded development and portability. Reference this issue in the embeded WG issue tracker to create a link to the portability WG.
Although this initiative currently looks somewhat stalled, I decided to mention this collaboration opportunity anyway, just like #9 and #10 do. See this for rationale: https://rust-lang.github.io/rust-project-goals/2025h1/build-std.html In theory, some portability...
Metadata
Owner
Metadata
Coordination repository of the portability Working Group (WG)