| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
uint32_t array_len) {I think it's good to pass the length here if we already read it, but we should add a DCHECK that `array->ulength().value()` is still equal to `array_len`.
Same for `PrintWeakArrayElements` and `ExtractWeakArrayReferences` below.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
uint32_t array_len) {I think it's good to pass the length here if we already read it, but we should add a DCHECK that `array->ulength().value()` is still equal to `array_len`.
Same for `PrintWeakArrayElements` and `ExtractWeakArrayReferences` below.
I changed `array_len` to be a parameter because not all types passed to this function derive from `FixedArray`, so `ulength()` is not always defined or could return uint32_t instead. My plan was to look at those after fixing all instances of FixedArray but since I am splitting the work into multiple CLs, I might do it in this one.
Should I add similar methods for WeakArrayList, PropertyArray, Context, etc?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
uint32_t array_len) {Arash KazemiI think it's good to pass the length here if we already read it, but we should add a DCHECK that `array->ulength().value()` is still equal to `array_len`.
Same for `PrintWeakArrayElements` and `ExtractWeakArrayReferences` below.
I changed `array_len` to be a parameter because not all types passed to this function derive from `FixedArray`, so `ulength()` is not always defined or could return uint32_t instead. My plan was to look at those after fixing all instances of FixedArray but since I am splitting the work into multiple CLs, I might do it in this one.
Should I add similar methods for WeakArrayList, PropertyArray, Context, etc?
Sounds good to me. Let's try adding `ulength` to the other types that need it. If it's not a huge change, we can inline it to this CL.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Arash KazemiI think it's good to pass the length here if we already read it, but we should add a DCHECK that `array->ulength().value()` is still equal to `array_len`.
Same for `PrintWeakArrayElements` and `ExtractWeakArrayReferences` below.
Omer KatzI changed `array_len` to be a parameter because not all types passed to this function derive from `FixedArray`, so `ulength()` is not always defined or could return uint32_t instead. My plan was to look at those after fixing all instances of FixedArray but since I am splitting the work into multiple CLs, I might do it in this one.
Should I add similar methods for WeakArrayList, PropertyArray, Context, etc?
Sounds good to me. Let's try adding `ulength` to the other types that need it. If it's not a huge change, we can inline it to this CL.
I added the methods and left TODOs to change the callers of length(). I also reverted the change on `ExtractWeakArrayReferences` as I don't see possible double fetches in the caller of the function.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |