perf(forge): avoid compiling for doc generation#15702
Merged
Merged
Conversation
mablr
approved these changes
Jul 13, 2026
mablr
left a comment
Member
There was a problem hiding this comment.
Cool, big gain on big projects like aave-v4.
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
forge doc, avoiding the ABI-only compiler process when every Solidity source is Solar-compatible.skipfilters on the fast path.solcnor documents skipped sources, while empty and mixed-version projects retain their fallback behavior.Benchmarks
Benchmarked release builds on Solady with 277 Solidity files. Each sample removed
out,cache, and both generated doc directories:The generated documentation is identical according to
diff -qr.