Ancestors

Written by Rob Napier on 2025-01-06 at 19:35

@robertryan I've been exploring your AsyncAwaitFuture for some production code. I've been puzzling over whether this can be made into an init on Future, so that the "awaitness" isn't in the type. I need it for a protocol conformance, but in general it feels this shouldn't be in the type.

It's not coming to me, though.

https://stackoverflow.com/a/78899940/97337

=> More informations about this toot | More toots from cocoaphony@mastodon.social

Toot

Written by Rob Napier on 2025-01-06 at 20:53

@mattiem I know you like a good concurrency puzzle; maybe this one will amuse you, bridging Combine with cancellation.

(@johnsundell, you may also be interested since you wrote on this without cancellation.)

=> More informations about this toot | More toots from cocoaphony@mastodon.social

Descendants

Written by Matt Massicotte on 2025-01-06 at 23:25

@cocoaphony @johnsundell Oh good this looks easy

=> More informations about this toot | More toots from mattiem@mastodon.social

Written by Matt Massicotte on 2025-01-07 at 12:36

@cocoaphony @johnsundell I played around with this a bit.

I cannot find any way to determine that self has been cancelled within an init on Future. I'm not ready to say this is impossible, but it's definitely hard enough that my Combine skills are insufficient.

=> More informations about this toot | More toots from mattiem@mastodon.social