Updated patch merges FormalParameterErrorLocations into the ExpressionClassifier as discussed offline. I tried to make a separate patch but it makes sense to
solve the arrow function stuff at the same time, and was gnarly to separate.
WDYT Dmitry?

There's one pending TODO in the patch to remove some of the checks when
re-parsing arrow function parameters in the full parser. The classifier should have ensured that they will parse, and so we should be able to DCHECK that the
expressions are of the right type.

https://codereview.chromium.org/1138153003/

--
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-dev
--- You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to