5 ms·
For anyone playing along at home, when the async/await RFC was accepted, it left the final syntax of "await" to be decided before stabilization. That was a litt
by steveklabnik 7y ago
For anyone playing along at home, when the async/await RFC was accepted, it left the final syntax of "await" to be decided before stabilization. That was a little over a year ago.
There was some debate, but it's been under pretty intense debate since at least November of last year. This has been the most discussed aspect of Rust ever. The tracking issue has 296 comments. There have been numerous threads on the internals forum, and recently, multiple threads on reddit per day. The team (which, I should note, I am not on) repeatedly asked for feedback, and read these threads, as well as participated in them.
It's been going in circles for ages. There are a few options with the syntax, but there's no clear standout winner; it really depends on how you weigh each pro and each con. At some point, though, it's the team's responsibility to decide. And so, on the sixth, they finally reached internal consensus. That's actually enough to just make the decision, but instead of just making the decision, they decided to go the extra mile, and say "here is our decision, and here are our reasons for reaching that decision. If you have something new to add to this incredibly long debate, please let us know, we'll be making the decision on the 23rd." : https://boats.gitlab.io/blog/post/await-decision/ https://boats.gitlab.io/blog/post/await-decision/ The internals thread on this post alone is 420 posts long: https://internals.rust-lang.org/t/a-final-proposal-for-await-syntax/10021 https://internals.rust-lang.org/t/a-final-proposal-for-await...
So yes, there are some vocal people who preferred a different syntax than the one that was chosen. Heck, I actually mostly prefer a different syntax. But at some point, a decision has to be made. Some people are not going to be happy with any decision. That's just how it is. It's not about "not listening to the concerns"; the concerns were listened to, but in the end, a different decision than (apparently) your preferred one was made. That's just how it goes sometimes. There are people who are equally passionate about this that would have been just as mad as you are now had the decision gone your way.
(I personally still wouldn't have made the call they did, but the call is reasonable. I've written code using it, and it's totally fine. I understand why the decision was made. We'll just have to see!)
- faryang1111 7y agoHow useful are these discussions? In the end, boats still prefers prefix and others still prefer postfix. This is pretty fake discussion. Everyone already has a position and pretend to be open to discussion.
- steveklabnik 7y agoThey exposed all the options. That’s very useful. They made their case. That’s very useful. This is the most discussed feature of Rust ever. The team spent a lot of time and energy on it, way way way more than any other feature. Several team members flip flopped positions several times.
- jnordwick 7y agoAnd the team seemed to ignore the users. The two polls I saw, both had the method syntax below 50% approval and below the other front runners. It seemed to me they basically said, "Sure, tell us want you want so we can note it and ignore it." Kind of a real dick move. Why bother even asking for input? (For disclosure, I preferred postfix punctuation similar to `?` that most people hated - so I'm not gettng my way either.)
- steveklabnik 7y agoFraming this as “the users” is disingenuous, again, a lot of users favored the decision too. The arguments of those users were taken into account, but the decision was made against it anwyay. Those polls were incredibly non-scientific, and don’t really mean anything.
- jnordwick 7y agoAnd you had better polling besides just your cohort and what other said to you? This seems like a disingenuous argument, ending with you can't really trust anything but our own opinions. Yes, they were bad, self-selecting polls. You have nothing better, and I hear far more complains than people being happy with the decision. The polls both tended to agree though so that would lend some credibility. Maybe you should have just explained "We aren't really asking the users since we have way to show that any poll would be valid, but we will take some input and make up our mind from that." I think that is a very precise (and charitable) description.
- 7y ago
- jkarneges 7y agoMost of the arguments may not be new, but given the overwhelming reaction to the recent blog post, I think it would be worth reflecting on that reaction and seeing if there isn't a reasonable way for the crowd to be heard. For example, I don't know if this was a new idea or an old one, but standardizing the general concept of dot-keyword before following through with dot-await, even if it ultimately doesn't change the decision, would make the decision easier to swallow (for me).
- steveklabnik 7y agoThe crowd was heard. There are also many people who are in favor of the syntax that was chosen! This is not a situation where the community is overwhelmingly settled on one thing and the team is settled on another. Yes, that has been discussed. It hasn’t been committed to in any way.
- deleted 7y ago[deleted]
- sanxiyn 7y ago> This has been the most discussed aspect of Rust ever. I still remember the lifetime syntax (&'a T) discussion. await syntax discussion felt really similar.
- steveklabnik 7y agoYeah, there’s just so many more people now. It’s possible that the ratio was the same, but the volume feels very different.