03b17d9af7
Summary: Many operations on references in JS can modify the referent by executing additional JS, including operations that we currently mark as const such as `getProperty`. Because of this, the current distinction between const and non-const operations on references like `jsi::Object` is somewhat arbitrary. A more consistent approach is to mark all operations as const, so that it is clear that the const-ness applies to the reference and not the referent. This is analogous to how smart pointers work, since something like `const shared_ptr<T>` only makes the pointer const, as opposed to `shared_ptr<const T>`. This also gives users better guarantees and more flexibility in where these references may be used. Changelog: [General][Changed] - Mark methods on JSI references as const. Reviewed By: fbmal7 Differential Revision: D41599116 fbshipit-source-id: 40b1537581b09c5a34d0928ee04e7db2b50d26ea |
||
|---|---|---|
| .. | ||
| jsi | ||
| .clang-tidy | ||
| BUCK | ||
| CMakeLists.txt | ||
| React-jsi.podspec | ||