ResourceT wraps async exceptions into syncrhonous exceptions causing it to misbehave with safe exceptions

[jappeace]

I had this background job I was expecting to be killed,
most logic ran into a resource block (it's the esqueleto-streaming package).

but once it get's kill exception it's wrapped into a synchronous resourcest exception:

ResourceCleanupException {rceOriginalException = Just AsyncCancelled, rceFirstCleanupException = SqlError {sqlState = "", sqlExecStatus = FatalError, sqlErrorMsg = "connection disconnected", sqlErrorDetail = "", sqlErrorHint = ""}, rceOtherCleanupExceptions = []}

could this in case of async exceptions also be wrapped into an async resourcest exception, so that the thread dies as expected?