Observing :clean is an implementation detail. The cancelling function is supposed to become a no-op after completion, therefore m/race considers it safe to call it on the race winner.

so even if the second task wins in the race, its canceller will still be called? did i understand it correctly?

yes, but it's accidental and you should not rely on that

According to the docstring “If any task succeeds, others are cancelled then race completes with this result.” I originally thought that the canceller of the winning task would definitely not be called.

it may or may not be called, no guarantees

okay, understand now. thank you for the quick reply!

The reason is because cancellation and completion may be concurrent, when it happens the task process must be able to resolve the race condition and handle the "completion then cancellation" scenario. It is therefore always safe for the parent process to cancel after completion, so it's allowed to do that if it's beneficial for the implementation.

Thank you so much for the detailed explanation! It might be best to add this explanation to the docstring or somewhere else? Otherwise, beginners like me might misunderstand the meaning of the m/race docstring.

This is expert-only material, as an application developer you're not supposed to write tasks manually

haha, I am now half an expert

thanks again

@U053XQP4S by writing tasks manually you mean writing tasks following the task spec without using missionary api (eg m/sp)?

yes