hyperlight-dev / hyperlight-dev/hyperlight

Consider renaming files named `mod.rs/x86_64.rs/aarch64.rs` to more unique filenames

Offen
#1,762 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
lifecycle/needs-review
Vorherrschende Sprache
Rust
Sterne
4.7k
Forks
208
Ø Merge
1 T. 7 Std.
Gemergte PRs (30 T.)
47

Beschreibung

Having multiple files with same name makes it annoying to search and find specific files.

For the `x86_64.rs/aarch64.rs` files (example `src/hyperlight_host/src/hypervisor/hyperlight_vm/x86_64.rs`) we could put them in a folder with that name instead (as we already do in certain places for example `src/hyperlight_host/src/hypervisor/regs/x86_64/special_regs.rs`).

For mod.rs file we can consider moving to the newer rust module convention which uses less mod.rs files.

I'm not saying all existing files must be renamed and are all bad, but I personally would like a bit more uniqueness

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Start by inventorying the `mod.rs`, `x86_64.rs`, and `aarch64.rs` files, including `src/hyperlight_host/src/hypervisor/hyperlight_vm/x86_64.rs`, and compare them with `src/hyperlight_host/src/hypervisor/regs/x86_64/special_regs.rs`. Determine which files can use the newer Rust module convention and which architecture files should move into uniquely named directories. Done means the agreed renames are applied consistently without breaking the project checks.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
rust
Bereich
developer-experience, operating-systems
Issue-Typ
Refactoring
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Aktiv
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
52/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.