it turns out there isn't a good way to handle function coloring to have a sync/async version of the same function/method. the convention is to just have a{something} versions that are async counterparts of the sync versions.
For all the stuff that's currently sync, the async version would just be a passthrough that calls the sync version. but then this allows customizing the async implementation when needed (where the sync version then becomes the passthrough, a little more cumbersome but still possible).
it turns out there isn't a good way to handle function coloring to have a sync/async version of the same function/method. the convention is to just have
a{something}versions that are async counterparts of the sync versions.For all the stuff that's currently sync, the async version would just be a passthrough that calls the sync version. but then this allows customizing the async implementation when needed (where the sync version then becomes the passthrough, a little more cumbersome but still possible).