Bug 1889120 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
I've noticed that some crashes are incorrectly being aggregated together (example: bug 1885339) because slice index accesses of slices (e.g., using a `2..4` "index" in the expr. `slice[2..4]`, which I'll refer to as "sub-slice accesses" to hopefully be more clear) are not part of the prefix list. The frames that don't already appear to be part of the prefix list are:

* `<core::ops::range::Range<usize> as core::slice::index::SliceIndex<[T]>>::index`
* `core::slice::index::<impl core::ops::index::Index<I> for [T]>::index`
Revision 1 by
on 
I've noticed that some crashes are incorrectly being aggregated together  because slice index accesses of slices (e.g., using a `2..4` "index" in the expr. `slice[2..4]`, which I'll refer to as "sub-slice accesses" to hopefully be more clear) are not part of the prefix list. The frames that don't already appear to be part of the prefix list are:

* `<core::ops::range::Range<usize> as core::slice::index::SliceIndex<[T]>>::index`
* `core::slice::index::<impl core::ops::index::Index<I> for [T]>::index`

Back to Bug 1889120 Comment 0