@@ -53,7 +53,7 @@ the respective issue):
5353- comment: how to guarantee affinity? seems to require an additional coroutine
5454- don't do?
5555
56- ## affine_on has no default spec
56+ ## ` affine_on ` has no default spec
5757
5858[ LB] ( https://github.com/lewissbaker/papers/blob/master/isocpp/task-issues.org#affine_on-is-missing-a-specification-for-a-default-implementation )
5959[ DK] ( https://github.com/bemanproject/task/blob/issues/docs/issues.md#affine_on-underspecified )
@@ -62,22 +62,22 @@ the respective issue):
6262- fix: say something specific
6363- comment: we don't have the tools to say what implementations can do for known senders
6464
65- ## affine_on semantics unclear
65+ ## ` affine_on ` semantics unclear
6666
6767[ LB] ( https://github.com/lewissbaker/papers/blob/master/isocpp/task-issues.org#affine_on-semantics-are-not-clear )
6868
6969- the wording is unclear
7070- fix: two versions
7171- comment: I think I had the 2nd in mind
7272
73- ## affine_on shape
73+ ## ` affine_on ` shape
7474
7575[ LB] ( https://github.com/lewissbaker/papers/blob/master/isocpp/task-issues.org#affine_on-might-not-have-the-right-shape )
7676
7777- ` affine_on ` should just depend on the receiver's ` get_scheduler() ` .
7878- comment: agreed - that is design, though
7979
80- ## affine_on: schedule vs. stop token
80+ ## ` affine_on ` schedule vs. stop token
8181
8282[ LB] ( https://github.com/lewissbaker/papers/blob/master/isocpp/task-issues.org#affine_on-should-probably-not-forward-stop-requests-to-reschedule-operation )
8383
@@ -86,7 +86,7 @@ the respective issue):
8686- comment: in case of ` set_stopped() ` the coroutine doesn't resume; for ` set_error(e) ` other reasons may exist
8787- comment: however, I don't object to this direction
8888
89- ## affine_on vs. other algorithms
89+ ## ` affine_on ` vs. other algorithms
9090
9191[ LB] ( https://github.com/lewissbaker/papers/blob/master/isocpp/task-issues.org#we-should-probably-define-customsiations-for-affine_on-for-some-other-senders )
9292
@@ -189,4 +189,4 @@ the respective issue):
189189
190190- legacy APIs may need TLS to be set appropriately
191191- objective: capture TLS before async, restore after
192- - fix: use custom affine_on with wrapped scheduler, delegating
192+ - fix: use custom ` affine_on ` with wrapped scheduler, delegating
0 commit comments