thread-safety definition

[Alexander Terekhov]

Ted Baker wrote:
[...]
> I thought you meant *compile* resolution of the overloading, so as
> to generate different call contexts of the same function name.
> Since your async_cancel{} code can have nested calls to arbitrary
> (separately compiled) code, you can't do that without
                       ^
                       |
async-cancel-safe -----+ (nested sync_cancel {} and no_cancel {}
aside for a moment).

> interprocedural control flow analysis (across separately compiled
> modules), which I don't believe gcc has any plans to do.  If you
> are talking about dynamic (runtime) dispatching, then you are ...

I'm NOT talking about dynamic (runtime) dispatching. Think of
const correctness.

regards,
alexander.