When initializing an object, the logic "zeros" the gaps between
the fields. I don't know why but I suspect it has to do with the
way interning works. The hash-consing of an object probably scans
the memory of the object at some point. The hash could give
different results if it included gaps with different values.
However, the interning in 32bits mode doesn't require this to
happen. So disabling it for now. It would probably be cleaner to
fix the math so that it also works in 32bits mode, but it's not
urgent.
Description
Motivation and Context
How Has This Been Tested?
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation change
Checklist:
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
When initializing an object, the logic "zeros" the gaps between the fields. I don't know why but I suspect it has to do with the way interning works. The hash-consing of an object probably scans the memory of the object at some point. The hash could give different results if it included gaps with different values.
However, the interning in 32bits mode doesn't require this to happen. So disabling it for now. It would probably be cleaner to fix the math so that it also works in 32bits mode, but it's not urgent.
Description
Motivation and Context
How Has This Been Tested?
Types of changes
Checklist:
docs/