Viacheslav Popov

So, PR with `goog.structs.Map` replaced with ES6 Map (and Set) will be accepted or it can break some internal CL usage and we should start with `@suppress {deprecated}` instead?

I don't see a reason to deprecate goog.structs.Map/Set without codebase refactoring in a first place. Right now I've just suppressed it in my Closure Library branch in places I use....