Default initialize properties in custom structs #52677
Open
+112
−82
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
If a native module spec declares a custom type:
https://www.internalfb.com/code/fbsource/[f6aeb413dbc3]/xplat/js/RKJSModules/Libraries/hsr/tm/code/editable_object/NativeEditableObjectModule.js?lines=151-154
The codegen will generate a c++ struct for that type, like so:
Problem
People can sometimes forget to default initialize this struct:
pthread.h
not found #2: D77182083In this scenario, all the members contain garbage data.
Changes
This diff ensures that all the members are always default initialized, like so:
This way, even if you forget to default initailize the struct, the members will still be default initialized.
Concerns/Risks
This could cause compilation issues in some of our existing native modules. (if one of the member types doesn't have a default constructor).
Code could start behaving differently, now that all the members are default initialized. (my hunch is that the risk from this causing a problem is low).
Changelog: [General][Changed] c++ tm codegen: Default initialize properties in custom structs
Reviewed By: christophpurrer
Differential Revision: D77315742