Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rename no_use_hack_collections to legacy_arrays
Summary: # What? Rename `no_use_hack_collections` to `legacy_arrays`. # Why? The thrift compiler options help describes this compiler option as follows: ``` DEPRECATED WARNING - Cannot be used with arrays, or stricttypes, must be used with arraysets. Generate array types in a clowny way, some may be legacy hack arrays while others normal hack arrays. ``` Based on the above description, `legacy_arrays` describe this option better. # Fixtures - Generated fixtures must not change. # Context `arraysets`, `no_use_hack_collections`, `stricttypes`, `array_migration`, `shape_arraykeys`, `const_collections` are all compiler options that control the generation of container fields. To make code generator simpler and easier to reason about, identify which of these can be removed/merged. The new options based on the ones that are currently in use: `legacy_arrays` replaces `no_use_hack_collections`. `hack_collections`, which was the implicit default in the absence of `arrays` and `no_use_hack_collections`, is now explicit. `arrays` will eventually become the default and cease to exist as an explicit option. # The steps The item in bold corresponds to the current diff. 1. Use new compiler options based on the ones that already exist. 1. Make arrays the default option. 1. Use the legacy arrays + hack collections logical equivalent of arrays. 1. Introduce hack collections wherever necessary. 1. Replace no use hack collections with legacy arrays. 1. Remove arraysets if arrays present. 1. **Rename `no_use_hack_collections` compiler option to `legacy_arrays`.** 1. Add `hack_collections` compiler option. 1. Remove references to the `arrays` compiler option. 1. Delete the `arrays` compiler option. Reviewed By: rmakheja Differential Revision: D67602754 fbshipit-source-id: 22cc9ae784f699847463e3d807091de13270ec42
- Loading branch information