You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Daniel Sun (Jira)" <ji...@apache.org> on 2019/08/29 07:26:00 UTC
[jira] [Updated] (GROOVY-9236) Avoid unnecessary resolving
[ https://issues.apache.org/jira/browse/GROOVY-9236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Sun updated GROOVY-9236:
-------------------------------
Description:
{{ResolveVisitor}}'s {{resolveFromStaticInnerClasses}}, {{resolveFromDefaultImports}} and {{resolveNestedClass}} will try to guess class qualified name and load. In the process, lots of time wasted on finding non-existing classes. So we should try to resolve classes in a determined manner.
For example,
For {{java.util.stream.Collectors}}, {{resolveFromStaticInnerClasses}} will try to guess {{java.util.stream$Collectors}}, {{java.util$stream$Collectors}}, {{java$util$stream$Collectors}}.
And {{resolveFromDefaultImports}} will guess {{java.lang.java$util$stream$Collectors}}, {{java.util.java$util$stream$Collectors}}, ..., {{groovy.lang.java$util$stream$Collectors}}.
After the precedence of resolving adjusted, the above unnecessary resolving can be avoided.
was:
{{ResolveVisitor}}'s {{resolveFromStaticInnerClasses}}, {{resolveFromDefaultImports}} and {{resolveNestedClass}} will try to guess class qualified name and load. In the process, lots of time wasted on finding non-existing classes. So we should try to resolve classes in a determined manner.
> Avoid unnecessary resolving
> ---------------------------
>
> Key: GROOVY-9236
> URL: https://issues.apache.org/jira/browse/GROOVY-9236
> Project: Groovy
> Issue Type: Improvement
> Reporter: Daniel Sun
> Assignee: Daniel Sun
> Priority: Major
> Fix For: 3.0.0-beta-4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{ResolveVisitor}}'s {{resolveFromStaticInnerClasses}}, {{resolveFromDefaultImports}} and {{resolveNestedClass}} will try to guess class qualified name and load. In the process, lots of time wasted on finding non-existing classes. So we should try to resolve classes in a determined manner.
> For example,
> For {{java.util.stream.Collectors}}, {{resolveFromStaticInnerClasses}} will try to guess {{java.util.stream$Collectors}}, {{java.util$stream$Collectors}}, {{java$util$stream$Collectors}}.
> And {{resolveFromDefaultImports}} will guess {{java.lang.java$util$stream$Collectors}}, {{java.util.java$util$stream$Collectors}}, ..., {{groovy.lang.java$util$stream$Collectors}}.
> After the precedence of resolving adjusted, the above unnecessary resolving can be avoided.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)