Well, if you try the reborrow example from the article with edition=2015 and RUSTFLAGS='-Zpolonius=next', you will see that it does indeed work. So the answer is yes.

The first thing these articles must mention is in which nightly SPECIFICALLY will the switch be made. Because it didn’t happen yet with the latest nightly, and (the PR that will flip the switch is not even merged yet ):

-Zpolonius=off

error: incorrect value `off` for unstable option `polonius` - either no value or `legacy` (the default), or `next` was expected

Also

NLL’s analysis is flow-insensitive.

Polonius Alpha passes this because its analysis is flow-sensitive

Always ask two+ people to proof-read your announcements before hitting publish.

Did you mean editions?

I don’t do Android (or much UI in general), but from what I gather, going with something like flutter_rust_bridge or membrane is probably the best route. The UI is not done in Rust. But it’s as close as you can get for non-toy use-cases, and without bringing a JVM language into the fray.

Toyota people apparently developed membrane for serious production use. But I haven’t used either, so I don’t have first hand experience to share.

Bro forgot to demangle. And now the kids are scared.