I think that the type checker is technically correct here. The RHS is correctly inferred (it's a `Map<String, String>`). And since you are trying to assign it to `Map<String, Object>` it fails. It's a consequence of inference of literals (Java doesn't have such literals so no such issues). You have to separate declaration from assignment, or use a cast.

2015-12-02 15:44 GMT+01:00 Winnebeck, Jason <Jason.Winnebeck@windstream.com>:
Is there a way to avoid awkward typing issues with literals as in this case:

void f() {
  Map<String, Object> x = [a: '1']
  println x + [b: 2]

This results in the following errors in 2.4.5:

[Static type checking] - Incompatible generic argument types. Cannot assign java.util.LinkedHashMap <java.lang.String, java.lang.String> to: java.util.Map <String, Object>
 at line: 3, column: 27

[Static type checking] - Cannot call <K,V> java.util.LinkedHashMap <java.lang.String, java.lang.String>#plus(java.util.Map <java.lang.String, java.lang.String>) with arguments [java.util.LinkedHashMap <java.lang.String, java.lang.Integer>]
 at line: 4, column: 13

It seems that the static compiler has issues with inferring RHS types. I think it might be similar to this case I run into from time to time:

void g(List<Integer> items) {}

void h() {

Results in:
[Static type checking] - Cannot call ConsoleScript6#g(java.util.List <java.lang.Integer>) with arguments [java.util.List <T extends java.lang.Object>]

Jason Winnebeck

This email message and any attachments are for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message and any attachments.