Re:Four limitations of Rust's borrow checker
by DylanSp on Tuesday December 24, 2024 @09:34AM
(#42502150)
Case 1 is definitely addressed by the Polonius-related work. There's a post [1] on the official Rust blog from 2023 about that, and this post [2] from Niko Matsakis' blog in June 2024 mentions that they were making progress on it, though the timeline has stretched out.
[1]: https://blog.rust-lang.org/inside-rust/2023/10/06/polonius-u...
[2]: https://smallcultfollowing.com/babysteps/blog/2024/06/02/the...
Re:Four limitations of Rust's borrow checker
by dccsillag on Tuesday December 24, 2024 @09:02AM
(#42501944)
(Side note)
That's odd, lobste.rs seems to be down for me, and has been like that for a couple of months now -- I literally cannot reach the site.
Is that actually just me??
EDIT: just tried some things, very weird stuff: curl works fine. Firefox works fine. But my usual browser, Brave, does not, and complains that "This site can't be reached (ERR_INVALID_RESPONSE)". Very very very weird, anyone else going through this?
Re:Four limitations of Rust's borrow checker
by yurivish on Tuesday December 24, 2024 @09:08AM
(#42501974)
Why Brave is blocked: https://github.com/lobsters/lobsters-ansible/issues/45
Re:Four limitations of Rust's borrow checker
by DaSHacka on Tuesday December 24, 2024 @12:00PM
(#42503121)
Looks as though it's not currently in effect, however?
https://github.com/lobsters/lobsters/issues/761
What a trite cat-and-mouse game, though at least it's entertaining to watch them try.
Re:Four limitations of Rust's borrow checker
by Permik on Tuesday December 24, 2024 @09:08AM
(#42501975)
Hello from Finland, I can reach the site all fine.
Hope you get your connection issues sorted :)
Re:Four limitations of Rust's borrow checker
by rascul on Tuesday December 24, 2024 @09:09AM
(#42501983)
Seems like lobste.rs might be blocking Brave.
Re:Four limitations of Rust's borrow checker
by porridgeraisin on Tuesday December 24, 2024 @09:20AM
(#42502065)
They are throwing a bit of a hissy fit over brave. Change the user agent or something and view the site.
Re:Four limitations of Rust's borrow checker
by ykonstant on Tuesday December 24, 2024 @10:45AM
(#42502622)
Reading the facts of the situation, it seems like a warranted "bit of a hissy fit".
Re:Four limitations of Rust's borrow checker
by hitekker on Tuesday December 24, 2024 @12:12PM
(#42503215)
Eh, pushcx's is right to disagree with past bad decision Brave made, but I think he's conflating a few grievances together. Someone tried to reason with him on that front, and it ended with them withdrawing from the community: https://lobste.rs/s/iopw1d/what_s_up_with_lobste_rs_blocking...
I sense some hidden ideology, but it's his community (and users) to own, not mine.
Re:Four limitations of Rust's borrow checker
by coffeeling on Tuesday December 24, 2024 @03:40PM
(#42504743)
It's not just that he disagrees with the things on an object, what happened level. He actively reads malice into every misstep to paint the organization as abusive.
Re:Four limitations of Rust's borrow checker
by porridgeraisin on Wednesday December 25, 2024 @08:11AM
(#42508630)
Yep.
Re:Four limitations of Rust's borrow checker
by sammy2255 on Tuesday December 24, 2024 @11:19AM
(#42502870)
Disagree. Regardless of what Brave is doing you shouldn’t block via User Agent like this.
Re:Four limitations of Rust's borrow checker
by gs17 on Tuesday December 24, 2024 @01:30PM
(#42503811)
Especially not simply making the site not load like that. If you really think a browser is so bad you don't want people using it, at least have it redirect to a message explaining what your grievance is. Unless the browser is DDoSing webpages it loads successfully, making the site look broken is pretty worthless as a response.
EDIT: Although, it looks like they tried to do that sometimes? No idea why they would switch from that approach.
1. Checking does not take match and return into account: I think this should be addressed by Polonius? https://rust.godbolt.org/z/8axYEov6E
2. Being async is suffering: I think this is addressed by async closures, due to be stabilized in Rust 2024/Rust 1.85: https://rust.godbolt.org/z/9MWr6Y1Kz
3. FnMut does not allow reborrowing of captures: I think this is also addressed by async closures: https://rust.godbolt.org/z/351Kv3hWM
4. Send checker is not control flow aware: There seems to be (somewhat) active work to address this? No idea if there are major roadblocks, though. https://github.com/rust-lang/rust/pull/128846
[0]: https://lobste.rs/s/4mjnvk/four_limitations_rust_s_borrow_ch...
[1]: https://old.reddit.com/r/rust/comments/1hjo0ds/four_limitati...