Follow convention for struct names in special_names
commitc619d2b5e497220b5ca2a9e73e8802cf382e6dc0
authorJake Bailey (Hacklang) <jakebailey@fb.com>
Fri, 28 Jan 2022 19:48:19 +0000 (28 11:48 -0800)
committerFacebook GitHub Bot <facebook-github-bot@users.noreply.github.com>
Fri, 28 Jan 2022 19:51:56 +0000 (28 11:51 -0800)
tree97071ee68df4c5f49e08ed6f52a04ebafc3e1135
parentb6c76321b93aa5b72abf56d490ea45ce43675603
Follow convention for struct names in special_names

Summary: As edwinsmith pointed out on {D33820141 (https://github.com/facebook/hhvm/commit/355891dcbf5964c6a075e0b9d1ebbe6e5c4db1f2)}, the convention for initialisms in struct names is to use PascalCase and treat the initialism as a word. The field names in this file also break convention, but since they will actually appear in typing logic, I figure there might be some value to keeping their casing the same as naming_special_names.ml for now. We can circle back and change them to snake_case later. Since these struct names won't appear in typing logic, there's no reason to keep the unidiomatic names, so let's fix them now.

Reviewed By: edwinsmith

Differential Revision: D33822374

fbshipit-source-id: ad623b5ab59b37b539316aa5a16de3121475d495
hphp/hack/src/rupro/lib/special_names.rs