A friend of mine was banging his head against the wall because this Groovy code. Let’s explain very quickly what this does. First, we create an empty map and then we define a key that is the result of a string interpolation. The key will be . "job-4" Then we verify if the key is already on the map. If the map does not have the key, we add it with the value , and then we do the same again, but just this time the key will be on the map and nothing will change. The value for key , should remain the same, that is value . 1 "job-4" 1 Let me tell you something, we are all wrong. The line will in fact, print . println(cache[key]) 2 This is madness!!! so we looked at other languages to see if one of them behaves in the same way Groovy does. In Ruby we do: it prints out the value as expected! 1 In JavaScript we do: it prints out the value as expected! 1 In Elixir we do: it prints out the value as expected! 1 In Scala we do: it prints out the value as expected! 1 What is wrong with Groovy!!!!??? The problem comes from the way Groovy manages dynamic typing and string interpolation. When Groovy does the string interpolation, the resulting type is which means the comparison is not in the way you expected. We need to force to be a be doing . GStringImpl GStringImpl String .toString() If we only do: def key = "job-${4}".toString() everything starts working as expected. Conclusions Stop using Groovy!!!

Too Long; Didn't Read

In your car, at home, or at work — Bosch technology shapes many areas of life.

What is wrong with Groovy?

Too Long; Didn't Read

Nicolas A Perez

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

What is wrong with Groovy?

Too Long; Didn't Read

Nicolas A Perez

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

RELATED STORIES