Compile time roadmaps#617
Open
nikomatsakis wants to merge 3 commits intorust-lang:mainfrom
Open
Conversation
Replace the `| Needs | Funding |` and `| Needs | Contributor |` metadata rows with dedicated `## Funding` and `## Help wanted` sections that use structured tables: - Funding: | Purpose | Cost | Status | with parsed USD amounts and emoji status indicators (🔍 Looking, 💬 Under discussion, ✅ Finalized) - Help wanted: | Task | Experience level | Time investment | Add funding table directives: - (((FUNDING TABLE))) — flat summary table - (((FUNDING TABLE: theme))) — filtered by roadmap - (((FUNDING TABLE GROUPED))) — grouped by roadmap with subtotals Costs are parsed ($25,000, $75K, $1.5M, TBD) and summed for subtotals and grand totals in the grouped table.
- Migrate 8 goals from `| Needs | Funding |` to `## Funding` sections - Migrate 8 goals from `| Needs | Contributor |` to `## Help wanted` sections - Add funding amounts from Tweede Golf (f16: $25K, tail-call: $25K, cg_clif: $75K) - Set funding statuses (finalized, under discussion, looking) - Split help-wanted page into contributors.md and funding.md subpages - Funding page uses grouped table with roadmap subtotals
…uilds Combine the two compilation-time roadmaps into a single "Fast Builds" roadmap. The goals overlap significantly (cg_clif, parallel frontend, crate slicing) and the distinction was more confusing than helpful. Update design axioms to capture real tradeoffs: - No one thing (many small improvements that add up) - End-to-end, not just the compiler (consider linking, Cargo, etc.) - Scenario matters (specialized wins for specific workflows like RDR) Add a ## Funding section to the roadmap using (((FUNDING TABLE: Fast Builds))).
celinval
reviewed
May 4, 2026
|
|
||
| ## Motivation | ||
|
|
||
| ### The status quo |
Contributor
There was a problem hiding this comment.
Is this goal meant to be compiler specific, or should it include cargo? If it includes cargo, I would add unnecessary re-compilation. Lack of shared cache.
Member
There was a problem hiding this comment.
My list, which is the basis of this PR, had cargo and caching.
|
|
||
| ### How we get there | ||
|
|
||
| | Goal | Timespan | What and why | |
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
3 participants
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.
Revisit our fundraising page and create a "fast builds" roadmap with @lqd as the POC
Rendered