chore(workspace): establish Rust foundation - #2
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements Phase 1 of the Roadrunner roadmap by establishing the Rust workspace and its initial crate boundaries without adding routing behavior.
roadrunner-coreas the library boundary for future graph, geographic, cost, and routing workroadrunner-cliwith theroadrunnerbinary as the application composition boundaryserde,thiserror, andtracingdependenciesCargo.lockLint policy
The workspace denies missing public documentation, unsafe code, unused lifetimes and qualifications, broken Rustdoc links, all default and pedantic Clippy findings, debug macros,
todo!,unimplemented!, andunwrap/expectusage.CI additionally promotes compiler warnings to errors.
Phase boundary
This PR intentionally contains no graph representation or routing algorithm. Those remain assigned to later roadmap phases. The core crate exposes only a minimal version boundary so the CLI can compile against it and the workspace dependency direction is exercised.
Validation
cargo fmt --all -- --checkcargo clippy --workspace --all-targets --all-features --locked -- -D warningscargo test --workspace --lockedcargo run --locked --bin roadrunnercargo metadata --locked --no-deps --format-version 1git diff --check main...HEADAll checks pass locally.