-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add os::fortanix_sgx::ffi module #57860
Conversation
r? @cramertj (rust_highfive has picked a reviewer for you, use r? to override) |
Looks good to me. It'd be nice if we could share these implementations among all platforms that use bytes for OS strings, and I'd greatly appreciate a follow-up PR that unifies those implementations into a single internal module, but in the meantime... @bors r+ |
📌 Commit 8db59d4 has been approved by |
🌲 The tree is currently closed for pull requests below priority 1000, this pull request will be tested once the tree is reopened |
I did think about this, but it's not super trivial. I guess some of these files (e.g.
Also, the stability attributes might differ. So, while the code is the same, the metadata around it isn't, and I'm not sure how to unify this into a single place. |
Add os::fortanix_sgx::ffi module This uses the same byte slice accessors that Unix has. The [ABI specifies](https://docs.rs/fortanix-sgx-abi/0.3.2/fortanix_sgx_abi/struct.ByteBuffer.html) byte slices.
Add os::fortanix_sgx::ffi module This uses the same byte slice accessors that Unix has. The [ABI specifies](https://docs.rs/fortanix-sgx-abi/0.3.2/fortanix_sgx_abi/struct.ByteBuffer.html) byte slices.
@jethrogb There could be one (internal) module for all platforms that use bytes, defining the extension traits, and then the various platform-specific modules could import and re-export the bits from those modules and provide their own top-level module documentation. The docs for the extension traits themselves don't need to vary by platform. |
Rollup of 9 pull requests Successful merges: - #57380 (Fix Instant/Duration math precision & associativity on Windows) - #57606 (Get rid of the fake stack frame for reading from constants) - #57803 (Several changes to libunwind for SGX target) - #57846 (rustdoc: fix ICE from loading proc-macro stubs) - #57860 (Add os::fortanix_sgx::ffi module) - #57861 (Don't export table by default in wasm) - #57863 (Add suggestion for incorrect field syntax.) - #57867 (Fix std::future::from_generator documentation) - #57873 (Stabilize no_panic_pow) Failed merges: r? @ghost
Unify OsString/OsStr for byte-based implementations As requested in #57860 r? @joshtriplett
This uses the same byte slice accessors that Unix has. The ABI specifies byte slices.