Christopher Hunt

> So, at a high level: I don't intend to force everyone using `metrics` to use `portable-atomic`. Practically speaking, does it provide equivalent behavior to `std` for architectures that don't...

> I do trust `portable-atomic`, but forcing every implementor to use it just... doesn't make sense. There's no technical reason why the atomics from the standard library aren't good enough,...

Hey @tobz - I'm happy to close out this issue if you'd prefer. I'm actually thinking of experimenting with an open-metrics implementation that is suitable for no-std/no-alloc environments and thus...

> > I’m unsure if you can “opt out” of the default features with cargo. > > You can, by setting `default-features` to `false` in `Cargo.toml`: > > ```toml >...

Here's the simplest reproducer I could find: ``` scala> :setting -unchecked scala> :paste // Entering paste mode (ctrl-D to finish) abstract class A { sealed abstract class B final case...

> The Vault team's preferred solution would be to properly support cache control via appropriate response headers. How would TTL be expressed when creating/updating a secret?

Why did we choose to have the special syntax to demark explicitly setting a property, and not the attribute instead (as per #1322)? Or have I misread? UPDATE: I see...

> > Why did we choose to have the special syntax to denote explicitly setting a property, and not the attribute instead (as per #1322)? Or have I misread? >...

Having followed the `cargo install` route, I note that the resultant `wasm-pack` is built for x86: ``` huntc@MBP14inch2021 ~ % file `which wasm-pack` /Users/huntc/.cargo/bin/wasm-pack: Mach-O 64-bit executable x86_64 ```

According to [Wikipedia](https://en.m.wikipedia.org/wiki/Newline) at least, line endings can be a single return character. Also, and what motivated me to raise this, the [W3C spec for server sent events](https://www.w3.org/TR/eventsource/) includes a...