Tracking Issue for RawOsError
#107792
Labels
C-tracking-issue
Category: A tracking issue for an RFC or an unstable feature.
T-libs-api
Relevant to the library API team, which will review and decide on the PR/issue.
Feature gate:
#![feature(raw_os_error_ty)]
This is a tracking issue for the raw OS error type alias, used in
io::Error::raw_os_error
andio::Error::from_raw_os_error
(both are stable APIs).std
used to assume that the OS error type (return byerrno
and such) is ani32
. This is however not the case on platforms like UEFI (which usesusize
). To ensure idiomatic and convenient handling of native errors without loosing information, theRawOsError
type is introduced to allow future ports of the standard library to use the correct error type for their respective platform. As this does not change the error type on already supported targets, this is a backwards-compatible change. Current software can still usei32
directly while theRawOsError
type alias is unstable. However, this feature should probably be stabilized before ports using a different type are merged, to allow software to be more easily ported.Public API
Steps / History
Unresolved Questions
Footnotes
https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩
The text was updated successfully, but these errors were encountered: