The suggested setup
- there are two related
fn-s:asyncand not - presumably with different names
- there is context tied to lexical scope at caller site: are we inside
asyncfn/block or not? - we'd like compiler to aid in selecting the right
fn- the aid can be as weak as a warning when a wrong
fnis used - or as strong as selecting the right one to call (somehow)
- the aid can be as weak as a warning when a wrong
seems also applicable to floating-point fast-math. Indeed
- there can be two/three/four versions of
sumorsqrtfunction - there can be local context at call site: do I prefer loose math or reproducible math
- it'd be nice for compiler to aid in selecting the right version of
sumorsqrtto call