tree a0468b2db81b8253740316958e7d5ff48a43d8ff
parent b18c73e981ca5f533fdc19a5b5c9db0aaf21eccf
author Nate Bosch <nbosch@google.com> 1648495697 -0700
committer GitHub <noreply@github.com> 1648495697 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJiQgxRCRBK7hj4Ov3rIwAA+D4IAFR49XEUvRt4/1XX0azMaeWs
 LjIY0BtXDDdxhFIUBG9qbuUGpM4KzENz3R33N4pARR4QM8UmtGn0jdBrA11SmT0N
 F6VW8/nd/lX3Bpylv7MnGJrrlHM5ozx6wBllx2NwYbo8FjkpeTGB4Hr3U7HKNUMt
 Kueh6pqa73DA+WxtEvOMrPBiZIuFTgMEC+eIgIioM4HJJJCmtrfTlQ1IiYiAH4lX
 uXpOC1PttzHqR0ImZXk6DANDssvqJLmcwj9v/alRF0hcelZ8Oh02dTz7Wq5T2gnx
 yGvTj0dbK2nNAzEaLz8TGrWjtlJqyzDLi6YPwCaFNHhcUK+Lh4B1GZ9WRZXyf5E=
 =wATJ
 -----END PGP SIGNATURE-----
 

Change the default propagateCancel argument (#213)

Closes #212

Authors are more likely to expect propagation, and not cancelling is
often a hidden inefficiency which may go unnoticed and untested.

Update the doc comment to focus on the 3 ways an operation can end - as
a value, an error, or a cancellation. This will hopefully make it more
clear that the `onCancel` callback does not relate to the cancellation
of the returned operation.