From: Jungkee Song [mailto:[email protected]]
> Right. We're defining an AsyncMap interface [1] which Cache interface and > CacheList interface are based off of. AsyncMap isn't spec'd yet in any place > than in the .ts file. A difficulty encountered is we don't have any IDL > construct for this yet. Any suggestion? Btw, IMO AsyncMap somehow should be > standardized in ES7? I don't understand how an AsyncMap "interface" (class) could exist and be generic---especially not as a language construct. Things are asynchronous for a reason, e.g. they require I/O to happen. No generic class could encapsulate that knowledge. E.g. what does the algorithm for `get` say in AsyncMap? For some async maps it will do file I/O; for others, network I/O; for others, they will ask the user for values. A definition for `get` in a generic AsyncMap would have to delegate to some kind of `get` hook, but that's pointless, since you already have a `get` hook, namely the `get` method you're in the middle of defining.
