This should almost certainly be accompanied by a diagnostic, and Swift is entirely capable of performing that diagnosis (self captured by an @escaping closure). So I recommend filing a bug report asking for it.
Ok, but aren't there many legitimate cases of @escaping closures capturing self? Wouldn't that be the case for many uses of Task? Seems the crux of this issue is that the object is going to be deallocated after deinit and there's no way to keep it alive, no?