PTAL
I don't think we should remove `kDefaultTag`, as it is used by other embedders. For them, a testing tag does not seem correct. But I added a comment that only embedders that don't use the heap sandbox should use it.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
lgtm
kDefaultTag,Can we put this behind !V8_ENABLE_SANDBOX? This should be available on the API and avoid future pitfalls our configurations.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Can we put this behind !V8_ENABLE_SANDBOX? This should be available on the API and avoid future pitfalls our configurations.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
7 is the latest approved patch-set.
The change was submitted with unreviewed changes in the following files:
```
The name of the file: include/v8-sandbox.h
Insertions: 3, Deletions: 2.
@@ -62,9 +62,10 @@
kInspectorTaskInfoTag,
kLastV8InternalTag,
- // A default tag to be used by embedders that don't use the V8 heap sandbox.
- // If the sandbox is enabled, type-specific tags should be used instead.
+#if !V8_ENABLE_SANDBOX
+ // Embedders that use the sandbox should use specific tags for each type.
kDefaultTag,
+#endif // !V8_ENABLE_SANDBOX
kLastObjectWrappableTag = 0x7ffc,
kZappedEntryTag = 0x7ffd,
```
[api] Enforce tag range for v8::Object::Wrap
Add static assertions and a DCHECK to ensure that the CppHeapPointerTag
used in v8::Object::Wrap is always within the kObjectWrappableTagRange.
Additionally, this CL removes all uses of
`CppHeapPointerTag::kDefaultTag` in V8.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |