An argument that I feel has strongly resonated in a few of these blog posts, iincluding @H2CO3's (without diving in to whether we should are shouldn't support this or that individual new feature) is that:
A lot of new features have been added (to nightly and stable), a decent portion of which have been stabilized, and that the ecosystem hasn't had time to experiment with how those features change the experience of writing Rust code, esp. with regards to Rust 2018.
Generally, I think in the vein of the OP (ie. the blog post) there is a strong argument in increasing the bar for how much scrutiny (and how high a complexity/benefit bar) an RFC should be subjected for say the next 6 months or a year, in that our opinions on many RFCs may change when we are writing code quite a bit differently (certain things like async
, we've already bitten the complexity bullet on at least wrt. reserving the keywords).
Similarly there are a fair number of features that folks have proposed that are still on nightly, and a lot of them I personally believe might substantially change how rust code is written on an ecosystem wide scale (such as try { ... }
blocks, irregardles of wrapping or not) but also async
, generators, etc, etc, etc, etc.
Stabilizing (or alternatively, would we "decide" we didn't want to stabilize a feature?) these nightly features falls in to the narrative of handling the Rust comunity's technical debt certainly from T-compiler
perspective, (but maybe sometimes from a T-lang
perspective?).
Aside: Some issues are unstable for reasons such as blocking on chalk
or another
compiler improvement, but AFAIK try
blocks aren't one of those?
As part of the ongoing discussions going on around Rust 2018 Edition and the Roadmap for
Rust in 2019, some sort of snapshot view of ongoing effort and implemented on nightly,
vs. unimplemented but in an accepted RFC would definitely be valuable towards helping bring
the wider rust community onto a similar page.
^ and more specifically, what is the blocker on things (contributor time, vs. X/Y/Z refactor).
I suspect a link might already exist documenting that, but I'm not aware of it.
That said, a lot of folks have ideas that they'd like to try, and to suggest that we "slow down" or "increase the burden" of RFCs might feel unfair to all the new rustacean's that have been invited in as part of the goal of releasing an edition---
On this path, I wonder if a stronger encouragement towards eRFC
s (experimental) and other sorts of "lower commitment" mechanisms might be a good compromise between a fairly obvious need to deal with accumulated debt and the desire to support, encourage, and harness the drive of contributors/users who have a particular issue they are passionate about.