I'm only just learning Rust so I don't know much about Rust development, but what are the chances that any of the suggestions listed at the end make it into the language?
I'd love to see RangeInclusive fixed in the manner described. Part of what's blocking such a fix is that we have hard backwards compatibility guarantees. We'd have to do some kind of edition-based transition, where ranges start desugaring to a different type in a new edition than they did in the previous edition. We could do that, and there are various discussions going on to consider such approaches, but we're somew…
My least favorite Rust type
81–90 of 298 posts
Re: My least favorite Rust type
#82Re: My least favorite Rust type
#83Earlier quoted context omitted.
How long do you think it takes to release a working prototype when you already have one?
Maybe he has different standards than you? I assume Jai will be similar to his games as far as attention to details goes. I would describe his games as having a maniacal attention to detail.
Re: My least favorite Rust type
#84Earlier quoted context omitted.
How long do you think it takes to release a working prototype when you already have one?
But he doesn't want to release a "working prototype", he wants to release a finished, polished language.
Re: My least favorite Rust type
#85Earlier quoted context omitted.
Just because it has been debated extensively doesn't mean it's not a wart. Having run into the "reverse range does not contain what you obviously expect it to contain" before and wasting a few hours on it, like many other people have and will continue to do in the future, definitely makes me want to call it a wart.
Rust tries to be conservative with its semantics. You can always create your own range type and implement a deref/from for it to convert it to Rust range.
Re: My least favorite Rust type
#86Earlier quoted context omitted.
How long do you think it takes to release a working prototype when you already have one?
Maybe he has different standards than you? I assume Jai will be similar to his games as far as attention to details goes. I would describe his games as having a maniacal attention to detail.
Re: My least favorite Rust type
#87Earlier quoted context omitted.
I don't think it's reasonable to make a comment like this without explaining why. He has designed a programming language, so it seems fair to assume he'd have an understanding of programming language design.
You got a link for the compiler for said programming language?
Re: My least favorite Rust type
#88Earlier quoted context omitted.
Because I can't download a compiler for his language and try out his ideas. I've designed fantasy programming languages, too, but you don't see me telling everyone on the internet that will listen to me about them, dragging other PL designers that have actually released working code through the mud as I do. It's a simple matter of put up or shut up.
I think that's a really toxic attitude. My thoughts about programming languages are still valid, even though I've never made one of my own. I have opinions about what works and what doesn't, based on experience using programming languages, and just because I haven't actually tried to write a compiler doesn't mean I should "shut up" about it. If you don't like his ideas (or him) just ignore them. No one's forcing you…
Re: My least favorite Rust type
#89Earlier quoted context omitted.
Most of the methods are constrained to types that implement PartialOrd.
What happens if I make a range bounded on one end by NaN?
Re: My least favorite Rust type
#90Earlier quoted context omitted.
Most of the methods are constrained to types that implement PartialOrd.
What happens if I make a range bounded on one end by NaN?