oxidecomputer / oxidecomputer/lpc55_support

Consider switching to `zerocopy` and `bitfield`?

Open
#24 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
13
Forks
7
PR merge metrics
No merged PRs in 30d

Description

This crate was written relatively early in the development of Hubris. Since then we've put much more effort into making crates like zerocopy and bitfield work with our system as opposed to packed_struct. It certainly works well enough but it could be worth the effort to switch to other crates just to avoid needing to know how another crate works.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

No files or tests are named in the issue. Start by locating the crate's packed_struct integration and compare the effort and system support for zerocopy and bitfield; done means a justified migration plan or an equivalent working replacement with existing behavior preserved.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.