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

Make the crate `no_std` #1

Closed
llogiq opened this Issue Mar 23, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@llogiq
Copy link
Owner

commented Mar 23, 2019

At least TinyArena and NanoArena should be no_std. We could add two features (no_std and alloc) to make the crate usable in those settings. The former makes the crate no_std and the latter enables the SmallArena type using the alloc crate for no_std+alloc usage.

@kpp

This comment has been minimized.

Copy link
Contributor

commented Apr 13, 2019

Features should add functionality not restrict it. So in case of no_std/std you will have to add std feature turned on by default to enable std functionality.

take a look at https://www.reddit.com/r/rust/comments/49hlsf/no_std_library_optionally_depending_onusing_std/d0rxllu?utm_source=share&utm_medium=web2x

@llogiq

This comment has been minimized.

Copy link
Owner Author

commented Apr 13, 2019

You're right. An alloc default feature should be sufficient.

llogiq added a commit that referenced this issue Apr 25, 2019

mk_*arena, default alloc feature
This introduces a default "alloc" feature without which this
crate is `no_std` compatible. This fixes #1.

Also the length fields have been extended so that a `TinyArena`
now allows for 65536 elements and a `NanoArena` for 256 elements.

The version has been updated to 0.3.0.

llogiq added a commit that referenced this issue Apr 25, 2019

mk_*arena, default alloc feature
This introduces a default "alloc" feature without which this
crate is `no_std` compatible. This fixes #1.

Also the length fields have been extended so that a `TinyArena`
now allows for 65536 elements and a `NanoArena` for 256 elements.

The version has been updated to 0.3.0.

llogiq added a commit that referenced this issue Apr 25, 2019

mk_*arena, default alloc feature
This introduces a default "alloc" feature without which this
crate is `no_std` compatible. This fixes #1.

Also the length fields have been extended so that a `TinyArena`
now allows for 65536 elements and a `NanoArena` for 256 elements.

The version has been updated to 0.3.0.

@llogiq llogiq closed this in #15 Apr 25, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.