My least favorite Rust type

Post by ComputerGuru » Tue, Sep 22, 2020, 2:38 AM UTC

coolreader18 wrote: post #216

viraptor wrote: post #161

So my first thought was "hey, why doesn't it take AsRef instead?" Then I checked the rust playground and... AsRef is not available for simple numbers, which I find confusing - since you can always reference an int, why isn't it?

I guess the same reason that `impl AsRef for T` isn't implemented. (Not sure exactly what that is, but that would probably be a better question to look into, since you could argue that `AsRef ` should be manually implemented for any std type T with your argument)

Post by rtpg » Tue, Sep 22, 2020, 2:45 AM UTC

pornel wrote: post #155

estebank wrote: post #12

For literals, clippy will catch this by default: error: this range is empty so it will yield no values --> src/main.rs:2:9 | 2 | let x = 5..0; | ^^^^ | = note: `#[deny(clippy::reversed_empty_ranges)]` on by default = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#reversed_empty_ranges help: consider using the following if you are attempting to iterate over this range in…

May be worth moving to rustc, because that's not just bad style, that's incorrect code.

Post by baby » Tue, Sep 22, 2020, 3:04 AM UTC

rtpg wrote: post #244

pornel wrote: post #155

Earlier quoted context omitted.

May be worth moving to rustc, because that's not just bad style, that's incorrect code.

I disagree, sometimes you end up building empty ranges in your code for valid reasons (as a result of math, for example). special casing a check on literals feels a bit like saying you can create an empty non-mutable vector.

Post by hobby-coder-guy » Tue, Sep 22, 2020, 3:34 AM UTC

lilyball wrote: post #219

dathinab wrote: post #185

Earlier quoted context omitted.

The problem is that his/her proposal also says that start Now consider the usability nightmare `(1..10).unwrap()` would be and `&slice[(1..10).unwrap()]` and `(1..10).and_then(|range| slice.get(range))` instead of `slice.get(1..10)`. That's the actual problem, not that `Range` implements iterator. Oh and most ranges are used ad-hoc (created and then directly consumed) so for many use cases going with Range + IntoIter…

> The problem is that his/her proposal … Please just use the word “their”. “his/her” is not just awkward but also not even inclusive, as there are many people who do not use “his” or “her” pronouns.

Post by lalaithion » Tue, Sep 22, 2020, 3:46 AM UTC

TillE wrote: post #209

ShroudedNight wrote: post #173

Range's idiosyncrasies and the antipathy to improving its ergonomics manifest in the issues raised against the project have been a capstone mental block to my investing emotionally in Rust. I continuously really want to like the language. The premise is good, a lot of the ideas are really compelling, but when it comes down to aspects I disagree with, I get a strong sense of Rust demanding that users subjugate themsel…

I was super excited about the idea of Rust but constantly frustrated trying to use it to write real code. I've basically decided to stay in my (ever-improving) comfort zone of C++ until Rust gets named/default arguments, which is my arbitrary litmus test for whether it's going to actually be a usable language for me.

    struct OptionsStruct {...}

    impl Default for OptionsStruct {...}

    impl Add for OptionsStruct {...}

    fn port(portnum : u16) -> OptionsStruct {...}
    fn timeout(millis: u64) -> OptionsStruct {...}
    fn maxconns(conns: usize) -> OptionsStruct {...}

    fn main() {
      ...
      // startServer("localhost", default())
      startServer("localhost", port(54321) + timeout(1000));
      ...
    }