Again though Range is meant for indexing. Also the use case is going to be much more strongly for variables, not constants.
-
-
I don't think that's how people are going to use it...or want to use it.
2 replies 0 retweets 4 likes -
Replying to @clairernovotny @jaredpar and
It's going to confuse people when they want to use it in a loop
3 replies 0 retweets 1 like -
Replying to @clairernovotny @onovotny and
Inclusive upper is just against the norm here for languages and ranges. Especially for indexing.
3 replies 0 retweets 2 likes -
I'm a C# dev, I don't find their usages intuitive either. And from the polls here it's fairly obvious I'm far from alone. We should do what's right for C# and C# devs.
5 replies 0 retweets 4 likes -
Replying to @Nick_Craver @onovotny and
Language design isn’t done by polls. It’s done by critically looking at the scenarios, existing code, other languages and letting that inform our process.
3 replies 0 retweets 3 likes -
Sure, but without any input at all you'll can also have a feature the design team loves that no one will use. We just couldn't be further apart on this one - I honestly hope it doesn't ship if exclusive. Because it does more harm than good if it's confusing to most people.
1 reply 0 retweets 1 like -
Replying to @Nick_Craver @onovotny and
Again I was strongly in favor of inclusive until we did the research. As were others all passionate .NET devs. We didn’t decide on exclusive becuase we wanted to upset people, we did it because that’s what the research showed was the right decision.
4 replies 0 retweets 5 likes -
Replying to @jaredpar @Nick_Craver and
IIRC
@rustlang team has also done an extensive research and concluded that exclusive ranges are more pragmatic.1 reply 0 retweets 1 like -
But Rust also decided that having only-exclusive was too limiting, and added inclusive with direct language support. I have high confidence if C# only does exclusive, it will realize a few years later that only having that option was insufficient and it will add 'inclusive'.
2 replies 0 retweets 1 like
We went three years without them, and nothing broke. Some stuff is just less convenient. 0..255 doesn’t work for u8, so you need to make the counter bigger and cast down, for example. Many are glad we now have them!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.