Skip to content

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

@Ben-PH

Description

@Ben-PH

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.?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions