God, the -1 comments on the Swift Evolution Result proposal are so depressing.
“I’ve never used this, I prefer Promises” - ok, well I don’t see your Promises proposal.
“Let’s not be hasty and add something half-baked” - hasty?! This is the 3rd or 4th iteration of this proposal!
“I’ve never used this, I prefer Promises” - ok, well I don’t see your Promises proposal.
“Let’s not be hasty and add something half-baked” - hasty?! This is the 3rd or 4th iteration of this proposal!
“We won’t need Result once we have async/await” - great, then we can deprecate it when we get those. That’s how evolution works.
“What’s the point if it doesn’t have language sugar” - sugar can easily be added after the ABI lockdown. New types can’t.
“What’s the point if it doesn’t have language sugar” - sugar can easily be added after the ABI lockdown. New types can’t.
“I don’t like the naming, I prefer x” - everyone prefers x or y or z. The names in the proposal are the ones that have a broad consensus. They were bikeshedded for weeks without any agreement on something better.
The process of evolution is iterative. Sometimes we have to add things that aren’t *quite* the thing we want in order to make progress.
If we aren’t prepared to take a step forward unless it takes us over the finish line then we will never go anywhere.
If we aren’t prepared to take a step forward unless it takes us over the finish line then we will never go anywhere.
