Greg Tatum

For what it's worth @ochameau, you currently could type in a search term for `debugger`, and then drop samples that contained it, it's a bit more work than the proposal.

I'm interested in working on this after #107, although I see that @sffc is currently assigned to it. I would like to start with filling out this issue with links...

This comment is for my notes as I look into the prior art. I plan on editing it with my research. ### DateTimePatternGenerator * [i18n/unicode/dtptngen.h ](https://github.com/unicode-org/icu/blob/master/icu4c/source/i18n/unicode/dtptngen.h) * [i18n/dtptngen.cpp](https://github.com/unicode-org/icu/blob/master/icu4c/source/i18n/dtptngen.cpp) * Example...

So here is an update on where I am with this: I've done a lot of the research on the prior art, and understanding the terminology. I'm currently working on...

One thing I am discovering is that the `components::Bag` does not allow for every configuration of available [date field symbols](https://unicode.org/reports/tr35/tr35-dates.html#Date_Field_Symbol_Table). I also wrote a script that collects every skeleton available...

I think this issue needs better scoping, and a break out of separate issues. I added the discuss to add it to the meeting agenda. If we don't have time...

The C-API for ICU4C provides a list of common skeletons. I think this was interesting enough to document for future work: https://unicode-org.github.io/icu-docs/apidoc/dev/icu4c/udat_8h.html e.g. ``` #define | UDAT_YEAR   "y"   | Constant...

https://github.com/gregtatum/talk-perf/tree/master/perf-examples

We could surface this type of information in the sidebar. I'm skeptical about adding another column to the already data-dense call tree. In order to support this as a column...

The more I think about this, the more I want different percentages for different types of analysis. I was looking at a `requestAnimationFrame` loop, and I started filtering and transforming...