So, as context parameters are still experimental, I have to opt-in (using the compiler flag "-Xcontext-parameters") when writing functions using them - no surprise here.
But when using a function from such a module, I’m still forced to opt-in, even though I never use the context(…)syntax in the current module. This “infectious” behavior is really annoying, it effectively prevents libraries form introducing context parameters now, because it forces all callers to opt-in as well.
I think this implementation is quite restrictive, and that the opt-in should be only required when using the context(…)syntax, not for dealing with code from other modules.