Skip to content

Use isize::MAX directly on type instead of module #207

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

Merged
merged 3 commits into from
Apr 6, 2020
Merged

Use isize::MAX directly on type instead of module #207

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a2d606f
Use isize::MAX directly on type instead of module
faern Apr 5, 2020
6cceae6
Fix usage of Global.alloc
faern Apr 5, 2020
1d517f8
Fix Global.realloc by changing to Global.grow
faern Apr 6, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/vec-alloc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -182,7 +182,7 @@ fn grow(&mut self) {
// we need to make. We lose the ability to allocate e.g. 2/3rds of
// the address space with a single Vec of i16's on 32-bit though.
// Alas, poor Yorick -- I knew him, Horatio.
assert!(old_num_bytes <= (::std::isize::MAX as usize) / 2,
assert!(old_num_bytes <= (isize::MAX as usize) / 2,
"capacity overflow");

let new_num_bytes = old_num_bytes * 2;
Expand Down