[GROOVY-2330] GString vs String equality in collections

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1-rc-3
• Component/s: groovy-runtime
• Assignee: Unassigned
• Reporter: Hans Dockter
• Created: 25/Nov/07 16:04
• Updated: 08/Mar/16 19:37
• Resolved: 08/Mar/16 19:37

Description

GStrings are one of the big groovy features. But there current equals behavior in collections makes them useless for many use cases. Very confusing is also the behavioral difference between lists and other collections.

All tests fail except the first one. (Tests run against rev 9408)

class StringVersusGStringEqualsInCollections extends GroovyTestCase {

    String string
    GString gString

    void setUp() {
        def g = 'g'
        string = 'groovy'
        gString = "${g}roovy"
    }

    void testEqualsInList() {
        assertEquals([string], [gString])
    }

    void testEqualsInSet() {
        assertEquals([string] as Set, [gString] as Set)
    }

    void testKeyEqualsInMap() {
        String someValue = 'somevalue'
        Map stringMap = [(string): someValue]
        Map gStringMap = [(gString): someValue]
        assertEquals(stringMap, gStringMap)
    }

    void testValueEqualsInMap() {
        String someKey = 'somekey'
        Map stringMap = [(someKey): string]
        Map gStringMap = [(someKey): gString]
        assertEquals(stringMap, gStringMap)
    }
}

Issue Links

• is related to: GROOVY-951 Accessing Map elements using a GroovyString
• relates to: GROOVY-2331 Println behavior for collections, strings and gstrings [minor breaking change]