Replies: 2 comments 3 replies
-
Hi @alexito4, you are correct that We are definitely open to clarifying some docs for the method. Feel free to open a PR with your ideas, and then we can give some feedback. |
Beta Was this translation helpful? Give feedback.
-
@alexito4 Indeed, I already stumbled upon this in the past. I'm wondering if "fire and forget" is perceived differently for native speakers. There is a good chance the the upcoming presentation & navigation APIs will automatically cancel presented/navigated effects when dismissing/popping. This includes |
Beta Was this translation helpful? Give feedback.
-
Hello!
I was migrating to the new async primitives and found myself wondering if they do follow structured concurrency properly. For
.task
and.run
that seemed quite obvious, but I had my doubts about.fireAndForget
..fireAndForget
description and name made me think it might have been tailored for similar usages asTask.detached
. I suspected that was not the case, since one barely needs that, but the documentation didn't clarify it for me. A quick read trough the source code showed me that all those primitives follow the same implementation and thus follow structured concurrency (❤️ ) but I run some tests to convince myself.I was thinking if it's worth adding a note on ?at least?
.fireAndForget
to clarify that it will be cancelled properly, even if we don't care about its result. It would also help my fear of this being not set in stone and changing in a future version 😆I'm happy making a PR with a suggestion, just wanted to know if you want to talk about this in the docs or is too much to explain.
Beta Was this translation helpful? Give feedback.
All reactions