You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Probably my opinion is wrong. I’ll share it with you though. I think making an unstable feature for using std::sys as public module is a good idea. Really! Such a good wrapper around OS, safe or unsafe, could be very useful for optimizations.
The text was updated successfully, but these errors were encountered:
If you need specific functionality, such as an abstraction around an OS feature please discuss on URLO](https://users.rust-lang.org/) (there may be existing crates covering your needs) or propose a more specific feature rather than exposing all std-internals.
"Could be very useful" is not sufficient explanation for us to understand what you need and it also sounds speculative.
If you need specific functionality, such as an abstraction around an OS feature please discuss on URLO](https://users.rust-lang.org/) (there may be existing crates covering your needs) or propose a more specific feature rather than exposing all std-internals.
"Could be very useful" is not sufficient explanation for us to understand what you need and it also sounds speculative.
Hi! Probably my opinion is wrong. I’ll share it with you though. I think making an unstable feature for using std::sys as public module is a good idea. Really! Such a good wrapper around OS, safe or unsafe, could be very useful for optimizations.
The text was updated successfully, but these errors were encountered: