[FEATURE REQUEST] Non-throwing `flatMapLatest`

[NickSudibor]

One very handy method is

func flatMapLatest<Output>(
    _ transform: @Sendable @escaping (Element) async throws -> Output
)

that returns simple output (not AsyncSequence) and cancels previous operation, as new input values are processed.

But unfortunately, it only takes throwing closure parameter. I assume it is due to cancellation mechanics. It implies that if operation could be cancelled, it should throw cancellation error. And every operation inside flatMap could be cancelled.
But closure could signal its cancellation by various means, as, for example, returning Result.failure(error).
In that case we are facing unnecessary try-catch boilerplate when reading sequence values. Would be great if we had method overload with non-throwing transform parameter.

It also means, that AsyncJustSequence should be modified, to take 'factory' initialization parameter, just like 'AsyncThrowingJustSequence'. Current init with plain value could be maintained as a convenience init over that.

[NickSudibor]

Hmmm, maybe mapToResult can be used in this case to mitigate the need of such operator

[NickSudibor]

With further investigation, i encountered a problem, that mapToResult is terminating sequence if error is thrown upstream. Maybe it is because upstream sequence terminates itself, despite presence of mapToResult further down the stream. Thats different from how Combine handles it, where such operator keeps whole stream alive even is the error is met.
Don't know if we can fix it, seems like default behavior of Apple's map.
So if mapToResult is not helpful, we should come back to returning Result from our flatMap, to keep the stream alive even if error conditions are met.
So original question arises, maybe non-throwing overload of flatMap is not a bad idea?