search

WICG / performance-measure-memory

performance.measureMemory API
Other
78 stars 13 forks source link

Define the standard set of memory types #7

Closed ulan closed 4 years ago

ulan commented 4 years ago

This addresses Issue #6 by making the value of the type field platform independent and removing implementation specific types like 'js' and 'dom'.

ulan commented 4 years ago

@annevk, @bzbarsky, @domenic: please take a look

domenic commented 4 years ago

I guess this moves away from the idea of UA-specific type values, toward cross-UA-comparable ones? If so, this makes sense to me. But it's probably good to get the others' opinions as to whether the definitions are precise enough to be interoperably implemented. I'm a bit unsure that UAs will be able to agree on a set of shared types, and a set of definitions for those types, so that's why the UA-specific values seemed easier.

ulan commented 4 years ago

Thanks for the comment @domenic. As discussed offline, this approach doesn't work.

Abandoning this PR and moving the discussion to https://github.com/WICG/performance-measure-memory/issues/6#issuecomment-594481389