Yeah. How does it works? This is my question. Maybe some MetaData?

Basically, inline means "take body of this function and put in call place"

and “function body” is a set of bytecode instructions on this stage

Of course, with additional processing like replacing returns with corresponding value usage at call site, processing non-local returns and type reification if requested.

emmm. If kotlin compiler analysis byte code on compile time... The Kotlin/js ?

Analysis js code at compile time?

in case of js the compiler obviously has a source code, isn't it?

Sorry that I have a poor English...

😳

I don't think so.

could you explain why it might be?

That's an interesing question. I guess with the new Frontend IR this should be a deal of frontend compiler and shouldn't actually concern platform-related backends. As for how it's done right now, I'm not sure as I didn't check that. But knwoing that even main IR is a recent feature, previously the only artifacts compiler had were platform output (JS, JVM bytecode, etc) and Kotlin-specific metadata, compiler has to transform the former to inline actual function.

Once again, these are solely my speculations.

The sources are not always available.

You mean Kotlin/JS sources are also compiled into bytecode?

Minified JS after DCE is far from "source" code 😄

KtJS 'bytecode' is JS.

But that's still JS source code. :)

for human of course, but not for compiler

It's rather a poor man bytecode for V8

I would assume there is some sort of IR in between KtJs sources and JS output anyway