oxidecomputer / oxidecomputer/hubris

Removing wildcard imports kind of stalled out.

Open
#1,894 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

developer-experience Triaged H2'26
Dominant language
Rust
Stars
3.6k
Forks
239
Avg merge
1d 12h
Merged PRs (30d)
23

Description

After achieving consensus with the team, in #1752 I started removing uses of wildcard imports (that is, use somecrate::*;) in Hubris. I'm using Clippy to try to avoid regressions in the areas where they've been removed.

But there's a lot of Hubris left, and new wildcard imports are occasionally still added (potentially by copy-paste from previous ones).

It would be nice to clean the rest of this up, and it would be nice to spread the work across more people than just me.

Contributor guide

Open the contributing guide

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

Review the wildcard-import cleanup described in #1752 and search the Hubris tree for uses of use somecrate::*;. Use Clippy to check the areas being changed and identify any regressions; the work is done when the remaining wildcard imports are removed and Clippy continues to pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
embedded-iot, operating-systems
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.