Repository navigation
Implement October 6 Dylints review - #1
Merged
Merged
Conversation
This branch was successfully deployed
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.
Implements the October 6 Dylints review.
This reorganizes the lint library and category hierarchy, updates Dylint discovery and catalog generation, and adds bounded build scheduling guidance to help prevent memory exhaustion. The workspace version is incremented to 0.3.0 for the breaking pre-1.0 changes.
Validation completed locally after rebasing on the latest
main:nix --accept-flake-config --max-jobs 1 --cores 1 develop --command cargo nextest run -p xtask --test benchmarksnix --accept-flake-config --max-jobs 1 --cores 1 fmtnix --accept-flake-config --max-jobs 1 --cores 1 develop --command cargo xtask release --base 0ed03375bd1190a44720a68f189fd9ca5fdf6710The full Nix flake check passed before the final rebase; the required GitHub checks will validate this exact commit.