Niko Matsakis, a Rust core team member, reflects on the challenge of reaching consensus in open source language design. The post argues that the goal of design discussions should be to 'map the solution space' rather than defend specific proposals. Using Rust's ? operator and ownership/borrowing model as examples, it explores how apparent binary tradeoffs can often be resolved by a third option — though never for free. The post critiques the current RFC process for starting with specific solutions, which encourages defensiveness, and hints at future posts exploring more structured approaches to collaborative design.
Table of contents
Beyond tradeoffsExample: the ? operatorThere is no free lunchRust’s origin storyTradeoffs after all – but the right onesMapping the solution spaceWhat does mapping the solution space really mean?Our current process mixes all of these goalsConclusionOh, one last thing…FeedbackFootnotes25 Impressions