Noted.
I also am not sure of the value of this diagnostic, what does this actually give you? It's a very rare situation to not have to worry about cancellation to spend such huge amount of compiler effort to warn about.
Well this topic is only a nitpic question really.
I just needed to know why as Swift Concurrency is to me the most elegant modern programming concept and it just feels like a rough edge that this mistake can be hidden in plain sight.
I guess it falls down to the relaxed rules of unstructured Tasks that’s all.
It would be better if instead the
Taskinitializer did not allow discarding the task handle, which was/is being discussed here: Pitch: Remove discardableResult from throwing task initializers
Love that.