[
https://issues.apache.org/jira/browse/GROOVY-10934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692265#comment-17692265
]
Eric Milles commented on GROOVY-10934:
--------------------------------------
[~blackdrag] Two reasons:
# Parser does not need to process tokens of imports supplied via config
# Resolver does not search for type in star import that does not have source
range; no highlighting/navigation/notification is possible when import in
implicit (not present in source text)
> Performance when Resolving Import Statement
> -------------------------------------------
>
> Key: GROOVY-10934
> URL: https://issues.apache.org/jira/browse/GROOVY-10934
> Project: Groovy
> Issue Type: Question
> Components: Groovysh
> Affects Versions: 3.0.5, 2.5.17
> Reporter: Ken Hu
> Priority: Major
> Attachments: Groovy10934.groovy
>
>
> The time it takes to resolve imports for scripts seems to have increased
> substantially since fixing the issue for GROOVY-5103. This can have a major
> impact on performance when a simple script that contains many imports is
> executed because the majority of the time will be spent resolving the
> imports. Are there any workarounds for this?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
