Re: how does the haxe3 new map works?

[Rudy G]

Hi,

Map needs two types : one for the key, one for the content.

For example, if you want a Map containing integers with strings as keys, you have to create it this way:

var map = new Map<String,Int>();

(well, there's StringMap for this example :P)

[davy zhang]

Hi, 

here this doc http://haxe.org/manual/haxe3/features#map

says:

I know I should put them together just like 

var map = new Map();

map["xxx"] = "yyy"; //will compile

also this works

var m:Map<String,String>; 

m = new Map();

m["ss"] = "mm";

Thanks~ 

As a bonus, maps allow element access with the Array operator:

var map = new Map();
map["foo"] = 9;
trace(map["foo"]); // 9
map["foo"] += 12;
trace(map["foo"]); // 21

[davy zhang]

Hi, 

here this doc http://haxe.org/manual/haxe3/features#map

says:

I know I should put them together just like 

var map = new Map();

map["xxx"] = "yyy"; //will compile

also this works

var m:Map<String,String>; 

m = new Map();

m["ss"] = "mm";

Thanks~ 

As a bonus, maps allow element access with the Array operator:

var map = new Map();
map["foo"] = 9;
trace(map["foo"]); // 9
map["foo"] += 12;
trace(map["foo"]); // 21

On Wednesday, February 19, 2014 8:03:48 PM UTC+8, Rudy G wrote:

[Rudy G]

When you create a Map using new Map(); (without <Type1,Type2>), the compiler adds those types using what you do with the map.

So when you do m["ss"] = "mm"; later, it assumes your map is a Map<String,String>

Using the new Map(); alone without doing anything with your map does not tel the compiler what kind of Map it is, so it fails