Skip to content

no_std support #336

@quodlibetor

Description

@quodlibetor

mentioned in 195, we need a good story around no_std/alloc support.

The parts of this that jump right to mind:

  • Breaking up the core mathy parts of chrono into their own crates/features
  • Refactoring various stringy bits to be in terms of Write
  • parts of chrono around parsing allocate, too, I believe.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions