Any updates on the iOS system wide ad blocking app?

Oooo neat, thanks !

What if I want to early return if there’s any error

The alternative to seem to be to just use a for loop or pay another iteration penalty like I did above…

Surely there’s a more elegant solution?

Gotcha, thx

Perhaps a dumb question but why do tokio locks not poison? Or do they and I’m just misunderstanding?

Thx!

Neat what does this actually mean? Is it like an additional 2fa layer of some sort?

Oh my god my eyes…why’s it hitting the

Who said this dosent happen? The lang is ment to help prevent issues not completely prevent issues. If you opt out of handling errors with unwrap you’re specifically asking the compiler to not help you. This is for cases where you have more context than the compiler and know this is okay.

Nil deref doesn’t exist then? How is an explicit unwrap any different?

For one of the lints you say you disallow aync locks. How would you deal with something like sqlite? I often have a tokio lock on a single write connection.

On that same note how do you deal with shared state? Do you just make a mpsc channel for every function that needs shared state?

Noted, that’s pretty neat. Yall got my vote. We might as well change the lang for the better and not suffer like cpp had to.

Yknow what I never really thought about it. Yeah I guess that does work. How do other crates handle this? If I take in tokio as an example and they use unwrap is that code safe as long as the crate specifies the edition?

Oo that could be interesting. I guess my question is do we deprecate unwrap?

*cowering in the fetal position* rust fixes this rust fixes this rust fixes this rust fixes this rust fixes this rust fixes this rust fixes this rust fixes this rust fixes this rust fixes this rust fixes this rust fixes this rust fixes this rust fixes this rust fixes this rust fixes this rust fi

This seems like a pretty big change would the ecosystem really be okay?