In ImportSpecifier, the two Identifiers can have overlapping location information about estree

[RReverser]

Such a duplication was brought to simplify handling of such shortenings and allow them to be processed just in the same way as a as a in AST tools. Why do you think that is an issue?

[sebmck]

@ikarienator Same goes for object property shorthand var obj = { x, y };. What do you propose is the solution?

[nzakas]

I think it's okay as it is. The object property shorthand that @sebmck references really helps with AST consumers.

[sebmck]

Yeah, agreed. Not even sure how you'd get around this without adding an
additional node type which I'd be strongly against.

On Thursday, 5 March 2015, Nicholas C. Zakas [email protected]
wrote:

I think it's okay as it is. The object property shorthand that @sebmck
https://github.com/sebmck references really helps with AST consumers.

Reply to this email directly or view it on GitHub
#42 (comment).

Sebastian McKenzie

[michaelficarra]

@sebmck: In the Shift AST, we made the name field optional: https://github.com/shapesecurity/shift-spec/blob/ce703795a855f66081242c7356547742b7e78fa4/spec.idl#L177-L180

[RReverser]

I'm closing this as "by design".