| 03:31 | <Steve Hicks> | also what kind of overriding they allow (we have AsyncContext.Snapshot.wrap for certain kinds of overriding, but I'm not sure whether or not this models everything) Along these lines - if there's not a clear choice between registration-time and some other context, then it may be worth remembering that you can always get the registration context using wrap no matter what option is chosen, but if the spec is to go with registraion context, then the other option is likely much harder to achieve in the use cases where it may be needed. |
| 11:02 | <littledan> | Along these lines - if there's not a clear choice between registration-time and some other context, then it may be worth remembering that you can always get the registration context using wrap no matter what option is chosen, but if the spec is to go with registraion context, then the other option is likely much harder to achieve in the use cases where it may be needed. I’m aware of this argument but I am not so sure we should weigh this “expressiveness” argument too highly in all cases. I expect most usages in application code to just take the default behavior, so getting that “right” seems like the overwhelming factor (unless there is a strong expressiveness motivation for a particular case). |