Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add Bump Allocator #831
Add Bump Allocator #831
Changes from 34 commits
d4f1d58
c2b019e
3deb3d8
b4bec3d
0267f88
5b87b12
605aafe
de3095b
d668dac
1d776d9
1ff4965
6bff7cd
46f0e1d
a608499
52d05de
d382bae
1c62e7f
68741fe
95adb71
80ee405
767f234
53af550
fb49543
b1c4de1
3ea81cc
509c9c4
8e8af79
2208229
f042526
bcf728b
6dade8f
ae097bf
f4e6a31
baceccd
560fe2f
c971868
13b8bd3
6b452a6
7fce248
b12c9f9
8e84f34
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the plan for
wee-alloc
? I mean, why even keep it in here? If there is some valuable trade-off between both of them we should add some info on it to the docs: https://paritytech.github.io/ink-docs/datastructures/dynamic-allocation.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tradeoff here is
.wasm
size vs. efficient use of memory.wee_alloc
is able to re-use freed memory, while thebump
allocator is not.I agree though, if we do keep both it would be valuable to document the trade-offs. I've opened use-ink/ink-docs#24.