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.
The
LoadMode
LoadModeTypesInfo
in thegoanalysis.Linter
says that the linter needs to resolve all the types.The
LoadMode
WithLoadForGoAnalysis
in thelinter.Config
says that the linter needs more information about dependencies and sizes.Each of these loading modes has an impact on how the linter can be executed, how the cache is used, and on the speed.
For example, if a linter uses the
LoadMode
LoadModeTypesInfo
in thegoanalysis.Linter
, this linter will no be able to analyze a single file with elements not defined in that file.Another example, the impact of the wrong load mode on the speed of
ineffassign
:The loading mode depends on the internal requirements of a linter, it's neither a way to optimize speed nor a way to allow a linter to be executed on a single file.
But if the loading mode is wrong, it has an impact on the capacities and the performance of a linter.