MemoryDistribution's C++ API would be clearer with `size_t` than `uint64_t`
Categories
(Toolkit :: Telemetry, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox104 | --- | fixed |
People
(Reporter: chutten|RustWeek, Assigned: perry.mcmanis)
Details
(Whiteboard: [telemetry:fog:m?][good next bug])
Attachments
(1 file)
C++ has an explicit integral type for representing the sizes of things in memory: size_t. We should totally be taking that in MemoryDistribution::Accumulate instead of uint64_t.
(( In at least some cases they're the same width anyway, but let's not pass up a chance to use types to communicate with our users ))
| Reporter | ||
Updated•3 years ago
|
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Comment 1•3 years ago
|
||
GleanMemoryDistribution in rust/glean core is i64, should I also be updating that to usize so I can move this to size_t as well? https://searchfox.org/mozilla-central/source/toolkit/components/glean/bindings/private/MemoryDistribution.cpp#53
I can just leave it if we prefer m-c only changes or if it would not be appropriate to change in glean
| Reporter | ||
Comment 2•3 years ago
|
||
This is just for the FOG-side changes where we can break the API and fix the consumers all at once.
My recommendation is to file a follow-up for the Glean SDK to consider that change.
| Assignee | ||
Comment 3•3 years ago
|
||
Comment 5•3 years ago
|
||
| bugherder | ||
Description
•