Suggestion: Do not mark BUILTIN_FILE as a precompilation dependency #271
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
include(BUILTIN_FILE)
is problematic becauseBUILTIN_FILE
is recorded as a dependency of the precompilation file. To see the problem, suppose JuliaInterpreter is precompiled for projectA
and then for projectB
using the same Julia version. Now importing JuliaInterpreter for projectA
again triggers precompilation becauseBUILTIN_FILE
is updated by projectB
.This is not a major issue in standard Julia environment until JuliaLang/julia#27418 is solved. However, this problem can already be observed in
jlm
which is a system image manager I wrote to solve the precompilation problem. It would be nice if JuliaInterpreter can go ahead and solve the problem before the precompilation problem is solved in Julia. Let me know if it makes sense to do so or there is a better way to fix it.