See https://www.github.com/Kotlin/KEEP/tree/context-receivers/proposals%2Fcontext-receivers.md

currentComposer

is also not dynamically scoped because

@Composable

can be thought of as

context(Composer)

Now I agree that the way CompositionLocals work now is dynamic, but honestly it is suboptimal! The same feature can be implemented in the language in a static way, if only we could combine contexts, something like this

typealias AndroidContext = @Composable context(Context,View,...)
// Then setContent is defined like this:
fun setContent(content: context(AndroidContext) () -> Unit)

// And libraries can add more stuff to the context...
typealias MaterialContext = context(AndroidContext, MaterialTheme)

context(AndroidContext)
fun MaterialTheme(body: context(MaterialContext) () -> Unit)

// And users can add more stuff to the context...
typealias MyContext = context(MaterialContext,MyDatabase)
context(MaterialContext) fun MyComponent(stuff: context(MyContext) () -> Unit){}

Also, to be clear, what I mean by "dynamic scope" is not that it is dynamically typed. Dynamic scope has been in languages like LISP and is a very old concept. The variable's value is defined not by it's lexical scope but by the scope of where the method is invoked. This does a better job of explaining than I can. https://prl.ccs.neu.edu/blog/2019/09/05/lexical-and-dynamic-scope/