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

Discussion: shall we make std an optional extension? #233

Open
Ben-PH opened this issue May 5, 2024 · 0 comments
Open

Discussion: shall we make std an optional extension? #233

Ben-PH opened this issue May 5, 2024 · 0 comments

Comments

@Ben-PH
Copy link

Ben-PH commented May 5, 2024

It seems to me that this project deserves to be a no-std crate by default. From what I can gather, only a few things rely on alloc (see also #220 ), with no reliance on the standard library, at least when it comes to the core-concepts being dealt with.

In terms of just HList, the only non-core items I came across is the into-vec implementation, and that should probably be updated to alloc-gated per #220

Is it worth being no-std first and foremost to maximize compatibility, adding no-std to the cargo-toml keyword list, etc.?

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