[Not serious] Language not unstable enough

[Hoverbear]

I mentioned on IRC to @bstrie that I built a fresh Raft which hadn't been bumped in 22 days and it still compiled.

This is obviously a bug. I'd like to propose we reopen #666 for good measure.

I'm sorry if this makes anyone mad. It was a minor point of joy to me and I'd like to thank everyone for their incredible work!

[LaylBongers]

+1 this, I was appalled when after a weekend away from a project, it still compiled AND worked as intended.

[bstrie]

There's been some concern in the community that a Rust without overwhelming, unceasing breakage is a betrayal of Rust's joie de vivre. It would be great if the developers could commit to some sort of "Instability Guarantee" to restore our faith in their leadership.

[bstrie]

As we speak I'm working on a patch that changes the fn keyword to func in order to deliberately break every Rust program that has ever been written. Accepting this change in a timely and efficient manner would be just the show of good faith that the community needs right now.

[Hoverbear]

@bstrie I propose something more complicated than something that could be fixed with a simple regex. We should implement hoisting one master, then decide it was a bad idea a few weeks later, just to keep things fresh.

[bstrie]

While we're at it, is it too late to change the name of the language? What is "Rust" supposed to stand for, anyway?

[LaylBongers]

@Hoverbear What if to allow a function to borrow a value, it must call "promise_to_give_it_back" before doing anything else?

[Hoverbear]

@bstrie Because it's where the metal interfaces with us air breathers.

[LaylBongers]

As well, is it too late to propose Rust support for the compile-time politeness enforcement feature that INTERCAL programmers enjoy?

[HeroesGrave]

I propose we rename isize/usize again.

[LaylBongers]

Additionally, I suggest that any code within an unsafe block should not be written in Rust. Unsafe blocks should instead be written in Malbolge to disincentivice using unsafe blocks.

[soltanmm]

Whatever the changes are, please ensure that they come with formal proofs of more headaches from the borrow checker.

[killercup]

Well, now that the breaking language changes are coming to an end, I suggest we instead focus on introducing breaking changes to the most popular crates with patch-level version bumps!

[tailhook]

I think we should introduce another "unsafe"-like construct. I.e. every non-pure function should be marked with "side_effects" marker.

[GuillaumeGomez]

Closures haven't changed in a while, we need to fix that !