---

This section details on the original issue you should resolve

<issue_title>False positive triggers for async_without_await, unneeded_throws_rethrows with override functions</issue_title>
<issue_description>### New Issue Checklist

• I've Updated SwiftLint to the latest version.
• I've searched for existing GitHub issues.

Bug Description

async_without_await, unneeded_throws_rethrows "false positive" triggers when function has override.

class A {
    func test() async {
        try? await Task.sleep(for: .seconds(0.5)) 
        print("A")
    }
}

class B: A {
    override func test() async { 
        print("B")
    }
}

Task {
    let b = B()
    await b.test()
}

The following code produces B as output, but when the rule is enabled, it suggests to replace to:

class B: A {
    func test() { 
        print("B")
    }
}

as a result, the output will be A, because it doesn't override the original function. So the rule breaks the logic.
The same happens for throws in unneeded_throws_rethrows rule.

I would suggest excluding the warning for functions that have override

$ swiftlint lint

Environment

• SwiftLint version: 0.63.0
• Xcode version: 26.0.1
• Installation method used: Universal macOS Binary
• Configuration file:

only_rules:
- async_without_await
- unneeded_throws_rethrows

Are you using nested configurations? If so, paste their
relative paths and respective contents.
</issue_description>

<agent_instructions>Ignore override functions in the async_without_await rule, that is, even if the function doesn't await anything, keep the async keyword.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@SimplyDanny For `throws` that's not a problem. Overriding function can omit the `throws` if the function doesn't actually throw. But you're right for `async`. It cannot be left out.