[jira] [Commented] (GROOVY-7834) Calling hashCode on IntRange iterates through all elements in the range.
[
https://issues.apache.org/jira/browse/GROOVY-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427674#comment-15427674
]
Anand commented on GROOVY-7834:
---
I am taking only lower and upper bound to generate hash code. Pairing function
grantees the output no to be deterministic. Have look at the pull request and
let me know
> Calling hashCode on IntRange iterates through all elements in the range.
>
>
> Key: GROOVY-7834
> URL: https://issues.apache.org/jira/browse/GROOVY-7834
> Project: Groovy
> Issue Type: Bug
>Reporter: howard zhang
>
> {code}
> new IntRange(0, Integer.MAX_VALUE-1).hashCode()
> {code}
> The above code takes a few seconds to complete.
> I believe the hashCode method is not overridden and it defaults to
> AbstractList which iterates through all elements. I don't think this should
> be the default behavior.
> http://grepcode.com/file_/repository.grepcode.com/java/root/jdk/openjdk/6-b14/java/util/AbstractList.java/?v=source
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GROOVY-7907) Cannot assign value of type java.lang.Object with varargs, parameterized method and @CompileStatic
[
https://issues.apache.org/jira/browse/GROOVY-7907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul King resolved GROOVY-7907.
---
Resolution: Fixed
Assignee: Paul King
Fix Version/s: 2.4.8
Proposed PR merged. Thanks for raising the issue.
> Cannot assign value of type java.lang.Object with varargs, parameterized
> method and @CompileStatic
> --
>
> Key: GROOVY-7907
> URL: https://issues.apache.org/jira/browse/GROOVY-7907
> Project: Groovy
> Issue Type: Bug
> Components: Static compilation
>Affects Versions: 2.4.7
> Environment: Groovy 2.4.7 (tested also with 2.4.4)
>Reporter: Marcin Zajaczkowski
>Assignee: Paul King
>Priority: Minor
> Fix For: 2.4.8
>
>
> Static compilation fails when method is parameterized and there are varargs
> arguments which are not used in the call.
> {code}
> Error:(9, 23) Groovyc: [Static type checking] - Cannot assign value of type
> java.lang.Object to variable of type Ext.
> {code}
> Simple classes to reproduce the problem:
> {code}
> public class FooInJava { //needs to be in Java, a class in Groovy works fine
> T create(Class type, Object... args) { return null; }
> }
> class Ext {}
> @CompileStatic
> class FooMain {
> static void main(String[] args) {
> Ext create = new FooInJava().create(Ext) //casting is required to
> make compilation pass
> }
> }
> {code}
> It only occurs if a class with unfortunate method signature is written in
> Java and static compilation is enabled. Casting to the right type helps.
> Originally spotted with Gradle - `ExtensionContainer.create(...)`.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] groovy pull request #385: GROOVY-7907: Cannot assign value of type java.lang...
Github user asfgit closed the pull request at: https://github.com/apache/groovy/pull/385 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (GROOVY-7907) Cannot assign value of type java.lang.Object with varargs, parameterized method and @CompileStatic
[
https://issues.apache.org/jira/browse/GROOVY-7907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427596#comment-15427596
]
ASF GitHub Bot commented on GROOVY-7907:
Github user asfgit closed the pull request at:
https://github.com/apache/groovy/pull/385
> Cannot assign value of type java.lang.Object with varargs, parameterized
> method and @CompileStatic
> --
>
> Key: GROOVY-7907
> URL: https://issues.apache.org/jira/browse/GROOVY-7907
> Project: Groovy
> Issue Type: Bug
> Components: Static compilation
>Affects Versions: 2.4.7
> Environment: Groovy 2.4.7 (tested also with 2.4.4)
>Reporter: Marcin Zajaczkowski
>Priority: Minor
>
> Static compilation fails when method is parameterized and there are varargs
> arguments which are not used in the call.
> {code}
> Error:(9, 23) Groovyc: [Static type checking] - Cannot assign value of type
> java.lang.Object to variable of type Ext.
> {code}
> Simple classes to reproduce the problem:
> {code}
> public class FooInJava { //needs to be in Java, a class in Groovy works fine
> T create(Class type, Object... args) { return null; }
> }
> class Ext {}
> @CompileStatic
> class FooMain {
> static void main(String[] args) {
> Ext create = new FooInJava().create(Ext) //casting is required to
> make compilation pass
> }
> }
> {code}
> It only occurs if a class with unfortunate method signature is written in
> Java and static compilation is enabled. Casting to the right type helps.
> Originally spotted with Gradle - `ExtensionContainer.create(...)`.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GROOVY-7906) groovy-2.4.7/bin/startGroovy: line 275: syntax error: bad substitution
[
https://issues.apache.org/jira/browse/GROOVY-7906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427530#comment-15427530
]
John Wagenleitner commented on GROOVY-7906:
---
I believe that will delete lines 274 through 275 from the file:
https://github.com/apache/groovy/blob/042950dc23257bbc65cd2258f2fd2a197a98f802/src/bin/startGroovy#L274-L275
What is odd is that it should only execute those lines if cygwin is detected,
but at least on Alpine 3.4.3 the {{`uname`}} command returns just "Linux" for
me. Would be interested to know what it returns for you [~typek_pb]
> groovy-2.4.7/bin/startGroovy: line 275: syntax error: bad substitution
> --
>
> Key: GROOVY-7906
> URL: https://issues.apache.org/jira/browse/GROOVY-7906
> Project: Groovy
> Issue Type: Bug
>Affects Versions: 2.4.7
> Environment: Alpine linux (=> no bash, busybox only)
>Reporter: Peter B.
>
> running groovy in alpine linux results in:
> {code}
> /tmp/groovy-2.4.7/bin/startGroovy: line 275: syntax error: bad substitution
> {code}
> as a workaround I'm running:
> {code}
> sed -ie '274,275d' /tmp/groovy-2.4.7/bin/startGroovy
> {code}
> prior to invoking groovy
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GROOVY-7713) CompileStatic checking fails with null returns
[
https://issues.apache.org/jira/browse/GROOVY-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Wagenleitner resolved GROOVY-7713.
---
Resolution: Fixed
Assignee: John Wagenleitner
Fix Version/s: 2.4.8
Thanks for reporting the issue.
> CompileStatic checking fails with null returns
> --
>
> Key: GROOVY-7713
> URL: https://issues.apache.org/jira/browse/GROOVY-7713
> Project: Groovy
> Issue Type: Bug
> Components: Static Type Checker
>Affects Versions: 2.4.4, 2.4.5
>Reporter: Scott Douglas
>Assignee: John Wagenleitner
>Priority: Minor
> Fix For: 2.4.8
>
> Attachments: Test1.groovy, Test2.groovy, Test3.groovy, Test4.groovy
>
>
> -
> TEST 1
> -
> {code}
> package test
> import groovy.transform.CompileStatic
> class TestClass {
> @CompileStatic
> void doTest() {
> Closure closure = {
> return "foo";
> }
> }
> }
> {code}
> Compiles fine.
> -
> TEST 2
> -
> {code}
> package test
> import groovy.transform.CompileStatic
> class TestClass {
> @CompileStatic
> void doTest() {
> Closure closure = {
> if ("bah".length() == 3) {
> return null
> }
> return "foo";
> }
> }
> }
> {code}
> ...gives...
> {code}
> groovyc Test2.groovy
> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup
> failed:
> Test2.groovy: 9: [Static type checking] - Incompatible generic argument
> types. Cannot assign groovy.lang.Closure to:
> groovy.lang.Closure
> @ line 9, column 29.
> Closure closure = {
>^
> 1 error
> {code}
> -
> TEST 3
> -
> {code}
> package test
> import groovy.transform.CompileStatic
> class TestClass {
> @CompileStatic
> void doTest() {
> Closure closure = {
> return null;
> }
> }
> }
> {code}
> ...gives...
> {code}
> groovyc Test3.groovy
> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup
> failed:
> Test3.groovy: 9: [Static type checking] - Incompatible generic argument
> types. Cannot assign groovy.lang.Closure to:
> groovy.lang.Closure
> @ line 9, column 29.
> Closure closure = {
>^
> 1 error
> {code}
> -
> TEST 4
> -
> {code}
> package test
> import groovy.transform.CompileStatic
> class TestClass {
> @CompileStatic
> void doTest() {
> Closure closure = {
> }
> }
> }
> {code}
> Compiles fine.
> -
> COMMENTS
> -
> All files were compiled with 'groovyc Test\[1234\].groovy'. I expected all
> tests to compile. I wouldn't have thought returning null would cause a static
> compilation failure since null is a valid String. Also, I expected test 3 and
> test 4 to be equivalent.
> The workaround appears to be to cast the closure, like:
> {code}
> Closure closure = (Closure) {
> ...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GROOVY-7713) CompileStatic checking fails with null returns
[
https://issues.apache.org/jira/browse/GROOVY-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427504#comment-15427504
]
ASF GitHub Bot commented on GROOVY-7713:
Github user asfgit closed the pull request at:
https://github.com/apache/groovy/pull/384
> CompileStatic checking fails with null returns
> --
>
> Key: GROOVY-7713
> URL: https://issues.apache.org/jira/browse/GROOVY-7713
> Project: Groovy
> Issue Type: Bug
> Components: Static Type Checker
>Affects Versions: 2.4.4, 2.4.5
>Reporter: Scott Douglas
>Priority: Minor
> Attachments: Test1.groovy, Test2.groovy, Test3.groovy, Test4.groovy
>
>
> -
> TEST 1
> -
> {code}
> package test
> import groovy.transform.CompileStatic
> class TestClass {
> @CompileStatic
> void doTest() {
> Closure closure = {
> return "foo";
> }
> }
> }
> {code}
> Compiles fine.
> -
> TEST 2
> -
> {code}
> package test
> import groovy.transform.CompileStatic
> class TestClass {
> @CompileStatic
> void doTest() {
> Closure closure = {
> if ("bah".length() == 3) {
> return null
> }
> return "foo";
> }
> }
> }
> {code}
> ...gives...
> {code}
> groovyc Test2.groovy
> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup
> failed:
> Test2.groovy: 9: [Static type checking] - Incompatible generic argument
> types. Cannot assign groovy.lang.Closure to:
> groovy.lang.Closure
> @ line 9, column 29.
> Closure closure = {
>^
> 1 error
> {code}
> -
> TEST 3
> -
> {code}
> package test
> import groovy.transform.CompileStatic
> class TestClass {
> @CompileStatic
> void doTest() {
> Closure closure = {
> return null;
> }
> }
> }
> {code}
> ...gives...
> {code}
> groovyc Test3.groovy
> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup
> failed:
> Test3.groovy: 9: [Static type checking] - Incompatible generic argument
> types. Cannot assign groovy.lang.Closure to:
> groovy.lang.Closure
> @ line 9, column 29.
> Closure closure = {
>^
> 1 error
> {code}
> -
> TEST 4
> -
> {code}
> package test
> import groovy.transform.CompileStatic
> class TestClass {
> @CompileStatic
> void doTest() {
> Closure closure = {
> }
> }
> }
> {code}
> Compiles fine.
> -
> COMMENTS
> -
> All files were compiled with 'groovyc Test\[1234\].groovy'. I expected all
> tests to compile. I wouldn't have thought returning null would cause a static
> compilation failure since null is a valid String. Also, I expected test 3 and
> test 4 to be equivalent.
> The workaround appears to be to cast the closure, like:
> {code}
> Closure closure = (Closure) {
> ...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] groovy pull request #384: GROOVY-7713: CompileStatic checking fails with nul...
Github user asfgit closed the pull request at: https://github.com/apache/groovy/pull/384 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (GROOVY-7912) MissingPropertyException when referencing a static import in a closure's optional parameters
M. Justin created GROOVY-7912:
-
Summary: MissingPropertyException when referencing a static import
in a closure's optional parameters
Key: GROOVY-7912
URL: https://issues.apache.org/jira/browse/GROOVY-7912
Project: Groovy
Issue Type: Bug
Affects Versions: 2.4.7
Reporter: M. Justin
Priority: Minor
A MissingPropertyException is thrown when calling a closure which references a
statically imported field in the value of an optional parameter for a closure.
Likewise, a MissingMethodException is thrown when referencing a statically
imported method in the same manner. This only occurs when calling the method
without specifying the optional parameter.
I have confirmed that this issue does not impact methods with optional
parameters.
The following code illustrates the issue:
{code}import static java.util.Collections.EMPTY_LIST
import static java.util.Collections.emptyList
Closure closureWithStaticImport = { List list = EMPTY_LIST -> }
Closure closureWithoutStaticImport = { List list = Collections.EMPTY_LIST -> }
try {
// An exception is thrown when the statically imported optional parameter is
not specified
closureWithStaticImport()
} catch (MissingPropertyException e) {
assert e.message == 'No such property: EMPTY_LIST for class: staticImportTest'
e.printStackTrace()
}
// No exception is thrown when the optional parameter is specified
closureWithStaticImport(EMPTY_LIST)
// No exception is thrown when the optional parameter is not statically imported
closureWithoutStaticImport()
void methodWithStaticImport(List list = EMPTY_LIST) {}
// No exception is thrown when a method's optional parameter uses a static
import
methodWithStaticImport()
Closure closureWithStaticImportMethod = { List list = emptyList() -> }
try {
// An exception is thrown when the statically imported optional parameter is
not specified
closureWithStaticImportMethod()
} catch (MissingMethodException e) {
assert e.message == 'No signature of method: staticImportTest.emptyList() is
applicable for argument types: () values: []'
e.printStackTrace()
}{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GROOVY-7166) Can't build Groovy project due to too long file name
[
https://issues.apache.org/jira/browse/GROOVY-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426854#comment-15426854
]
Stefán Freyr Stefánsson commented on GROOVY-7166:
-
There is quite some time since this was reported but in case anyone stumbles in
here (as I did) I'd like to add that this may have been due to ecryptfs.
Groovyc seems to be generating filenames that are too long for the 143
character max limitation of that.
For more info see: https://bugs.launchpad.net/ecryptfs/+bug/344878
I had this problem when trying to compile the IntelliJ IDEA community project.
When I moved the directory out of my (encrypted) home directory, I was able to
compile it.
The problem here seems to be that groovyc is not querying the filesystem for
the max filename lenght. As mentioned in the above ecryptfs bug report, groovyc
should be using the statfs() syscall to query for the max filename length which
will be correctly reported as 143 by ecryptfs filesystems and should take
actions accordingly if generated files exceed that limit.
> Can't build Groovy project due to too long file name
>
>
> Key: GROOVY-7166
> URL: https://issues.apache.org/jira/browse/GROOVY-7166
> Project: Groovy
> Issue Type: Bug
>Affects Versions: 2.3.7
>Reporter: Marcin Grzejszczak
>Priority: Minor
>
> When I clone groovy-core and execute
> {noformat}
> ./gradlew clean test
> {noformat}
> I get:
> {noformat}
> :compileTestGroovy
> warning: [options] bootstrap class path not set in conjunction with -source
> 1.6
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> 1 warning
> startup failed:
> /home/marcin/repo/groovy-fork/target/test-classes/org/codehaus/groovy/ast/builder/AstBuilderFromSpecificationTest$_testSwitchAndCaseAndBreakStatements_closure31_closure120_closure124_closure128_closure129_closure130_closure131.class
> (File name too long)
> /home/marcin/repo/groovy-fork/target/test-classes/org/codehaus/groovy/ast/builder/AstBuilderFromSpecificationTest$_testForStatementAndClosureListExpression_closure36_closure154_closure156_closure160_closure161_closure162.class
> (File name too long)
> {noformat}
> Executed with JDK7 and JDK8. On Linux Mint.
> _uname -a_ execution result:
> {noformat}
>
> Linux someName 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014
> x86_64 x86_64 x86_64 GNU/Linux
> {noformat}
> A workaround is to move the repository to another folder to shorten the path.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (GROOVY-7900) uninstall.exe possibly contains trojan (or false positive)
[ https://issues.apache.org/jira/browse/GROOVY-7900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426403#comment-15426403 ] Keegan Witt edited comment on GROOVY-7900 at 8/18/16 4:57 PM: -- Kaspersky's latest definitions seem to no longer flag this executable (tested using https://scan.kaspersky.com, and then re-analyzed in VirusTotal). [~jfhumann] is it still causing you issues? I haven't found yet where to report false positives on Panda's site. was (Author: keegan): Kaspersky's latest definitions seem to no longer flag this executable (tested using https://scan.kaspersky.com). [~jfhumann] is it still causing you issues? I haven't found yet where to report false positives on Panda's site. > uninstall.exe possibly contains trojan (or false positive) > -- > > Key: GROOVY-7900 > URL: https://issues.apache.org/jira/browse/GROOVY-7900 > Project: Groovy > Issue Type: Bug >Affects Versions: 2.4.7 > Environment: Windows 10 >Reporter: Jan-Fabian Humann >Assignee: Keegan Witt > > I installed groovy windows installer from the official download page: > http://www.groovy-lang.org/download.html > Kaspersky Endpoint Security 10 flags uninstall.exe in the groovy folder as > Trojan-Ransom.NSIS.Onion.yjd and deletes it. > To verify I installed groovy in a Windows 10 VM without Kaspersky and > uploaded the file to https://www.virustotal.com/ and this is the report I got: > https://virustotal.com/de/file/a3686f92af80b7ad97c4a36065a9468c90b69479105fcc952c2227cd0c4a5548/analysis/ > 3/55 Anti Virus programs flag this file as virus/suspicious. > Could you please investigate whether you download server/install program/etc > has been compromised or it is a false positive? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GROOVY-7911) Chained multiple assignment parsing fail
[
https://issues.apache.org/jira/browse/GROOVY-7911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniil Ovchinnikov updated GROOVY-7911:
---
Description:
{code}
def a, b, c, d
(a, b) = [1, 2]
(c, d) = (a, b) = [1, 2] // fails, ')' expected after 'a'
(c, d) = a = (a, b) = [1, 2] // works though
{code}
was:
{code}
def a, b, c, d
(a, b) = [1, 2]
(c, d) = (a, b) = [1, 2] // fails, ')' expected after 'a'
(c, d) = a = (a, b) = [1, 2]
{code}
> Chained multiple assignment parsing fail
>
>
> Key: GROOVY-7911
> URL: https://issues.apache.org/jira/browse/GROOVY-7911
> Project: Groovy
> Issue Type: Bug
> Components: parser
>Reporter: Daniil Ovchinnikov
>
> {code}
> def a, b, c, d
> (a, b) = [1, 2]
> (c, d) = (a, b) = [1, 2] // fails, ')' expected after 'a'
> (c, d) = a = (a, b) = [1, 2] // works though
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GROOVY-7911) Chained multiple assignment parsing fail
Daniil Ovchinnikov created GROOVY-7911:
--
Summary: Chained multiple assignment parsing fail
Key: GROOVY-7911
URL: https://issues.apache.org/jira/browse/GROOVY-7911
Project: Groovy
Issue Type: Bug
Components: parser
Reporter: Daniil Ovchinnikov
{code}
def a, b, c, d
(a, b) = [1, 2]
(c, d) = (a, b) = [1, 2] // fails, ')' expected after 'a'
(c, d) = a = (a, b) = [1, 2]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GROOVY-7900) uninstall.exe possibly contains trojan (or false positive)
[ https://issues.apache.org/jira/browse/GROOVY-7900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426403#comment-15426403 ] Keegan Witt commented on GROOVY-7900: - Kaspersky's latest definitions seem to no longer flag this executable (tested using https://scan.kaspersky.com). [~jfhumann] is it still causing you issues? I haven't found yet where to report false positives on Panda's site. > uninstall.exe possibly contains trojan (or false positive) > -- > > Key: GROOVY-7900 > URL: https://issues.apache.org/jira/browse/GROOVY-7900 > Project: Groovy > Issue Type: Bug >Affects Versions: 2.4.7 > Environment: Windows 10 >Reporter: Jan-Fabian Humann >Assignee: Keegan Witt > > I installed groovy windows installer from the official download page: > http://www.groovy-lang.org/download.html > Kaspersky Endpoint Security 10 flags uninstall.exe in the groovy folder as > Trojan-Ransom.NSIS.Onion.yjd and deletes it. > To verify I installed groovy in a Windows 10 VM without Kaspersky and > uploaded the file to https://www.virustotal.com/ and this is the report I got: > https://virustotal.com/de/file/a3686f92af80b7ad97c4a36065a9468c90b69479105fcc952c2227cd0c4a5548/analysis/ > 3/55 Anti Virus programs flag this file as virus/suspicious. > Could you please investigate whether you download server/install program/etc > has been compromised or it is a false positive? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GROOVY-7834) Calling hashCode on IntRange iterates through all elements in the range.
[
https://issues.apache.org/jira/browse/GROOVY-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426284#comment-15426284
]
ASF GitHub Bot commented on GROOVY-7834:
GitHub user upadhyayap opened a pull request:
https://github.com/apache/groovy/pull/386
Calculating hashCode of IntRange by pairing function
https://issues.apache.org/jira/browse/GROOVY-7834?jql=status%20%3D%20Open%20AND%20project%20%3D%20Groovy%20AND%20type%20%3D%20Bug%20ORDER%20BY%20created%20DESC
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/upadhyayap/incubator-groovy GROOVY-7834
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/groovy/pull/386.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #386
commit 256a9f462b066cd4a2dfc124c0fb6c5b4edfccd8
Author: Anand upadhyay
Date: 2016-08-18T11:09:00Z
Calculating hashCode of IntRange by pairing function
> Calling hashCode on IntRange iterates through all elements in the range.
>
>
> Key: GROOVY-7834
> URL: https://issues.apache.org/jira/browse/GROOVY-7834
> Project: Groovy
> Issue Type: Bug
>Reporter: howard zhang
>
> {code}
> new IntRange(0, Integer.MAX_VALUE-1).hashCode()
> {code}
> The above code takes a few seconds to complete.
> I believe the hashCode method is not overridden and it defaults to
> AbstractList which iterates through all elements. I don't think this should
> be the default behavior.
> http://grepcode.com/file_/repository.grepcode.com/java/root/jdk/openjdk/6-b14/java/util/AbstractList.java/?v=source
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] groovy pull request #386: Calculating hashCode of IntRange by pairing functi...
GitHub user upadhyayap opened a pull request: https://github.com/apache/groovy/pull/386 Calculating hashCode of IntRange by pairing function https://issues.apache.org/jira/browse/GROOVY-7834?jql=status%20%3D%20Open%20AND%20project%20%3D%20Groovy%20AND%20type%20%3D%20Bug%20ORDER%20BY%20created%20DESC You can merge this pull request into a Git repository by running: $ git pull https://github.com/upadhyayap/incubator-groovy GROOVY-7834 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/groovy/pull/386.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #386 commit 256a9f462b066cd4a2dfc124c0fb6c5b4edfccd8 Author: Anand upadhyay Date: 2016-08-18T11:09:00Z Calculating hashCode of IntRange by pairing function --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
