-
Notifications
You must be signed in to change notification settings - Fork 434
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
core
wanted features & bugfixes
#514
Comments
I could only find a single function that is neither generic nor |
Right! I'm experimenting implementing two
|
This came from the original list I had in the other issue, where they were examples of the general idea of partitioning |
I have opened a PR to remove 128-bit features: rust-lang/rust#103126. |
Thanks! Added. |
Before we add more Adding configuration code doesn't necessarily affect statically linked binaries as much, as those will either be stuck with the code also, for each that actually uses it, or dead-code-eliminate it, and statically linked binaries include some of the use-cases that want the smallest size (such as embedded code which isn't running on an OS at all, not even an RTOS, and thus has limited options for dynamic linking and is usually just one blobby image). |
This may come in handy at some point down the line https://github.com/Amanieu/rfcs/blob/core-detect/text/0000-core_detect.md |
Following up the discussion here, I'd like to add two
Although @nbdd0121 mentioned these should be |
Sounds good, thanks! Language features are in #354 (I had |
@ojeda about the |
+1, I think @vincenzopalazzo wanted to mention it to the macros working group too. |
In theory the new macro metavar expression |
I finally had the time to start discussing the |
Thanks! Added. |
Note: there is the "A-rust-for-linux" label in the
rust
repository: https://github.com/rust-lang/rust/labels/A-rust-for-linux.Features that we would like to see
Required (we almost certainly want them)
core::panic::Location
(or a flag to ensure there is a\0
after thestr
s).file!()
, it is fine, since we can easily transform those withc_str!
(which we already do), so it is a nice to have (see the related item below).core::panic::Location::file
rust-lang/libs-team#466.core::panic::Location
file strings rust-lang/rust#117431.Nice to have (not critical, we could workaround if needed, etc.)
Disabling 128-bit features.
Disabling floating-point features.
f32
etc.).cfg
to disable formatting of floating point): core: add unstable no_fp_fmt_parse to disable float formatting code rust-lang/rust#86048.Disabling Unicode features / a way to use external tables.
Clarify invariants of the
Layout
type.Layout
to "a layout suitable to an allocated object"? Is it library / language UB? (currently it appears to be the former).Layout
type documentation.c_stringify!
,c_concat!
,c_file!
macros.c_str!
macro to then doc_str!(stringify!(...))
orc_str!(concat!(...))
.Clarify
addr_of!
documentation about whether it creates read-only pointers or not.Low priority (we will likely not use them in the end)
core
ones.Atomic
rust-lang/rust#130539.Atomic<T>
rust-lang/libs-team#443.Atomic<T>
type alias rust-lang/rust#130543.Done (stabilized, fixed, not needed anymore, etc.)
Ensure
no_fp_fmt_parse
builds are warning-free.no_fp_fmt_parse
builds are warning-free rust-lang/rust#105811.Ensure
no_global_oom_handling
builds are warning-free.core
underno_global_oom_handling
rust-lang/rust#110652.Bugs that we would like to see fixed
Required (we almost certainly want them)
Nice to have (probably not critical, we could workaround if needed, etc.)
Low priority (we will likely not use them in the end)
Done (stabilized, fixed, or not needed anymore, etc.)
Fix warning when libcore is compiled with no_fp_fmt_parse rust-lang/rust#105434.
Fix
no_global_oom_handling
build.Inline floating-point methods to avoid requiring intrinsics.
midpoint
,next_up
,next_down
are not marked as#[inline]
, which makes them appear under-Os
arm64, see Zulip: https://rust-for-linux.zulipchat.com/#narrow/stream/288089-General/topic/v6.2E11-rc1.20doesn't.20build.20for.20arm64/near/455637364.{f32,f64}::{next_up,next_down,midpoint}
inline rust-lang/rust#128749.The text was updated successfully, but these errors were encountered: