Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Replace no_use_hack_collections_ with legacy_arrays_
Summary: # What? Replace `no_use_hack_collections_` with `legacy_arrays_`. # Why? As mentioned in the context, `legacy_arrays_` replaces `no_use_hack_collections_`. # 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: yfeldblum Differential Revision: D67586860 fbshipit-source-id: ffa1160f4f29770b40c6b36ff664584a513590d7
- Loading branch information