Skip to content
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

(no_)global_oom_handling should be a feature #18

Open
remexre opened this issue Sep 14, 2024 · 0 comments
Open

(no_)global_oom_handling should be a feature #18

remexre opened this issue Sep 14, 2024 · 0 comments

Comments

@remexre
Copy link

remexre commented Sep 14, 2024

It'd be helpful if I could get allocator-api2 to behave as if cfg(no_global_oom_handling) was set, without actually having to switch to nightly, rebuild libcore/liballoc, etc. for it.

I think this might best be done by:

  • Adding an enabled-by-default global_oom_handling feature
  • Switching existing #[cfg(not(no_global_oom_handling))]s to #[cfg(all(not(no_global_oom_handling), feature = "global_oom_handling"))]
  • Maybe adding a pub const somewhere to expose whether the feature ended up being enabled (I want to assert elsewhere that it was not).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant