Using dynamic classes in strict is not a parse error
commitd33bb88a15f4923e7e0ede1260d9b68fad21832c
authorJosh Watzman <jwatzman@fb.com>
Wed, 21 May 2014 18:25:10 +0000 (21 11:25 -0700)
committerJoelMarcey <joelm@fb.com>
Thu, 22 May 2014 18:15:42 +0000 (22 11:15 -0700)
tree901677a10d7460aeeb7d433d27a60650cc8df9ed
parent63653413749b99effcc48059d723b766080cf81c
Using dynamic classes in strict is not a parse error

Summary: We need to move anything like this after parsing, so that you
can `UNSAFE` it. @KendallHopkins ran into this specifically.

Reviewed By: @pikatchu

Differential Revision: D1341785
hphp/hack/src/naming/naming.ml
hphp/hack/src/parsing/parser_hack.ml
hphp/hack/test/typecheck/method_dispatch_37.php [new file with mode: 0644]
hphp/hack/test/typecheck/method_dispatch_37.php.exp [new file with mode: 0644]