André Mello

To provide some additional context, my end goal is to be able to capture metrics while disconnected from a Prometheus instance. Producing the OpenMetrics format with timestamps is how Prometheus...

> The reason I expose as little as possible is two fold: > > 1. It keeps the crate simple, a small surface makes it easier to understand the crate...

> Why don't you use the Prometheus Push Gateway? > > https://prometheus.io/docs/practices/pushing/ The use case for that is different, it's for getting around network limitations rather than backfilling. In fact,...

Not to revive this discussion, but I recently came across [std::path::Component](https://doc.rust-lang.org/std/path/enum.Component.html), which comes from solving the same problem in a more specialized context. It's all about sometimes there being a...

I'm not sure I understand the motivation behind emitting a root token. Can you add some examples showing why that is useful? (I don't think I've run into any, or...

`std::path::Component` is a great analog here, but I think the motivation for it may not apply to JSON Pointers, precisely. That's because, as defined in RFC 6901, pointers are always...

Awesome! I think you meant the rename for 0.5 though? We are at 0.4.x releases.

> For documentation: > > We should probably solve theses issues by defining the include field in cargo manifests to zip up the protobufs in the crate tarball. > >...

Note echoed from #38 - we need to mock registry interactions so we can test local logic independently of it.

> What if use something like a singleton? I.e. I can implement a struct that will have a one-field `response`. The initial state of this field will be null (None),...