Swift Concurrency: Conforming a 3rd party library to actor isolation

Question

I am in the process of converting some code bases over to using Swift concurrency and am running into a few snags along the way.

The current project I'm working through has a few 3rd party libraries that it relies on, and in one of those libraries, there is a delegate protocol that requires some data values to be returned from its methods.

Here is an example of the type of delegate methods in the library:

public protocol FooDelegate: AnyObject {
    func foo() -> CGFloat
}

I'm attempting to return some values from the implementation of the protocol like this:

extension ViewController: FooDelegate {
    func foo() -> CGFloat { // <- Cannot satisfy requirement from protocol
        view.bounds.height
    }
}

Without any modification, the above is implicitly isolated to the MainActor and can not satisfy the requirement from the FooDelegate protocol.

One solution I've tried was to mark the function implementation with nonisolated:

extension ViewController: FooDelegate {
    nonisolated func foo() -> CGFloat {
        view.bounds.height // <- Cannot be referenced from a non-isolated context
    }
}

This did not work though because it references the view controller's view. That results in the view being referenced from a non-isolated synchronous context. (There are also a few other issues with this since any values that are passed through into any of the delegate functions need to conform to Sendable to be able to be passed across actors).

My question is, is there a way to take a 3rd party library and extend it somehow so that it conforms to proper actor isolation without having to modify its source code?