-
Notifications
You must be signed in to change notification settings - Fork 8
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
Build the standard library with different cargo features #4
Comments
If we expose some control over this, I think it will be limited to |
cfg
settings
Yes, that is what I meant. I think this originally started as a broader thought about portability issues ( |
Use case: Opt-in support for having |
I'm not sure if this is intended or accidental (i didn't see it mentioned in unstable docs or cargo test suite) but it is currently possible to specify features on libcore directly, like this : |
This is a "use case" issue to try to clarify and discuss a use case, and how it will be addressed.
There has been some interest in being able to pass different cargo feature flags to the standard library to change it some way; either to change the implementation, or to disable sections of the library.
This is unlikely to be possible with Cargo's current features system. There are some problems with backwards-compatibility, and generally the level of commitment to stabilize a feature flag would likely be extremely high.
Please leave a comment if you have any specific use cases to consider. Some that have come up in the past:
force-tiny-fmt
to use a different algorithm forfmt
.std
already has a number of cargo features (panic, backtrace, profiler, etc.).backtrace
can maybe be helpful in reducing binary size?This issue is to explore possible features, how they can be expressed from Cargo, and whether or not it is feasible to accomplish in a stable way.
This is partially related to #8.
The text was updated successfully, but these errors were encountered: