discarded_futures not lints inside a function that is inside unawaited

[westito]

Describe the issue
When async function wrapped into unawaited, the discarded_futures not lints inside the wrapped function. In this example activate should linted because if not awaited, the try-catch will not catch the exception.

To Reproduce

Expected behavior
activate function is linted in unawaited

[mateusfccp]

IMO this is the expected behavior, as you are explicitly telling that we don't want do wait for the future.

[bwilkerson]

My interpretation would be that the unawaited means you don't want to await the future returned by guarded (the argument to the function). But I would expect notification related to the future returned by activate because it's in a separate closure, and I don't think the unawaited outside the closure should impact the checking inside the closure.

[westito]

IMO this is the expected behavior, as you are explicitly telling that we don't want do wait for the future.

I don't want to wait for the outer Future, but I want to await the inner Future (it makes sense because if not awaited, the try-catch won't catch the exception)

My interpretation would be that the unawaited means you don't want to await the future returned by guarded (the argument to the function). But I would expect notification related to the future returned by activate because it's in a separate closure, and I don't think the unawaited outside the closure should impact the checking inside the closure.

Yes, that is what i'm saying.

[lrhn]

The discarded_futures lint it's generating a lot of reports, probably because its name doesn't match its meaning.

The description of what the lint does it's to warm if you call an asynchronous function, one which returns a future, in a non async(or async* presumably) function.

There are no exceptions. Using unawaited should not make any difference. It's probably good that it does, but the documentation should say so.
As written, it doesn't matter if or how you use the future.
If you call any function which returns a future, anywhere, the surrounding function must be async! That is it.

I agree that the activate should be a warning in any case.