Performance optiomize a CLI compile

[cdietrich]

We have the following scenario.

• we a dsl that describes data structures (like classes)
• we have a 2nd dsl that operates on these datastructures
• we have a compiler that operates on the 2nd dsls

in the compiler we do the following

• create documents for all files and add them to LangiumDocuments
• call documentBuilder.build(categegory: builtin)

besides the parsing times we se also linking makes up a notable part of the the compile time
i wonder if there is a nice way of avoing this.
as the ratio of the 2nd dsl / first dsl is just 10% or so
i wonder if we somehow can skip the eager linking of the first dsl files
in the build or if there is another away of having
the first dsl parsed+indexed (so that scoping can find them)
without using document builder

[spoenemann]

Let's add eagerLinking to the BuildOptions. We should make clear in the comments that eager linking is necessary for complete linking errors in the validation/diagnostics.

@cdietrich would you like to make a PR for this?

[cdietrich]

but we also want to eager link the files of the 2nd dsl. so i wonder if there is scenarios/examples that avoid using of the builder and still use linking/indexing

[spoenemann]

Yes you can't have reference descriptions without linking first. But those are only necessary in a language server scenario where you need an analysis of which documents are affected by a change.

You can invoke the builder multiple times with different documents and different options.

[cdietrich]

in our tool there is no state.
so once built we are done.

[spoenemann]

👍 then having an option to skip linking & reference indexing would help.

[cdietrich]

Yes but we might want to do it for some files only. Will for now try to hook into the different phases