Skip to content
Browse files

Rename phases to be more user-friendly

Summary: Phase names like "naming" and "type decl" are rather opaque to the end user. I figure that it would help people understand what Hack is doing if we named these to be more descriptive.

Reviewed By: pittsw

Differential Revision: D7033770

fbshipit-source-id: 855692cab0220582f362d4c8e93dbc782e3928aa
  • Loading branch information
arxanas authored and hhvm-bot committed Feb 21, 2018
1 parent a28afc0 commit 5f48311759b4c499ec358ab91a7dfd19080a9ec2
Showing with 3 additions and 3 deletions.
  1. +3 −3 hphp/hack/src/client/
@@ -117,13 +117,13 @@ let msg_of_tail tail_env =
else if matches_re parsing_re line then
"[parsing" ^ (count_suffix line) ^ final_suffix
else if matches_re naming_re line then
"[naming" ^ final_suffix
"[resolving symbol references" ^ final_suffix
else if matches_re determining_changes_re line then
"[determining changes]"
else if matches_re type_decl_re line then
"[type decl" ^ (count_suffix line) ^ final_suffix
"[evaluating type declarations of" ^ (count_suffix line) ^ final_suffix
else if matches_re type_check_re line then
"[type check" ^ (count_suffix line) ^ final_suffix
"[typechecking" ^ (count_suffix line) ^ final_suffix

0 comments on commit 5f48311

Please sign in to comment.