Investigate no_std support

Open
  • Is something wrong?
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
tooling

Research direction

Start by reviewing the json-five-rs crate's dependency configuration and identifying where standard-library support is assumed. Determine whether no_std support is useful and what implementation constraints it introduces. Done should be a documented feasibility decision with a clear scope for any follow-up implementation.

Written by the indexing model from the issue text.

Description

Basically, title. I'm not sure who, if anyone, needs this in a json5 parser, what it takes to implement, and what considerations I should make.

Dominant language
Rust
Stars
20
Forks
1
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from spyoungtech/json-five-rs

All issues in spyoungtech/json-five-rs

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.