Skip to content

liballoc should bubble up out-of-memory errors #18292

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.

Sign up for GitHub

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

Jump to bottom
Closed
thestinger opened this issue Oct 24, 2014 · 0 comments · Fixed by #18406
Closed

liballoc should bubble up out-of-memory errors #18292

thestinger opened this issue Oct 24, 2014 · 0 comments · Fixed by #18406
Labels
A-allocators Area: Custom and system allocators C-enhancement Category: An issue proposing an enhancement or a PR with one.

Comments

@thestinger
Copy link
Contributor

The decision to abort or fail on out-of-memory should be made as high up in the stack as possible.
@thestinger thestinger added A-libs C-enhancement Category: An issue proposing an enhancement or a PR with one. A-allocators Area: Custom and system allocators labels Oct 24, 2014
@thestinger thestinger mentioned this issue Oct 28, 2014
Merged
bors added a commit that referenced this issue Nov 2, 2014
@bors
auto merge of #18406 : thestinger/rust/oom, r=cmr
a294b35 
This makes the low-level allocation API suitable for use cases where
out-of-memory conditions need to be handled.

Closes #18292

[breaking-change]
lnicola pushed a commit to lnicola/rust that referenced this issue Oct 17, 2024
@bors
Auto merge of rust-lang#18292 - roife:fix-issue-17427, r=Veykril
d4e5c24 
feat: handle self-param outside of methods when renaming

close rust-lang#17427
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-allocators Area: Custom and system allocators C-enhancement Category: An issue proposing an enhancement or a PR with one.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

bubble up out-of-memory errors from liballoc
1 participant
@thestinger