Taylor Fausak

I run into this problem with `(&)`. Example [input](https://github.com/tfausak/octane/blob/4a4f9fbd46b91610b78d1cbf379bc2369e75caa4/library/Octane/Type/Int32.hs#L61): ``` haskell instance BinaryBit.BinaryBit Int32 where getBits _ = do bytes >>` or `

I like that approach. I prefer some indentation of the operators since it's required with `do` notation. How would it work with parentheses? Using Chris's example from above, I see...

Yeah, I think `then`/`else` needs to be indented, but the problem here is that the indentation *inside* the `then`/`else` is context sensitive. Everything after the `else` should be bumped down...

Definitely looks that way! Based on that issue, upgrading to `elm-syntax` at least version 7.0.6 should fix this problem.

My PR ( #45) is very similar to this, but sets the upper bound at `< 2.1` rather than `< 3`.

See #354, #300, and #223. This is the expected behavior: > When you run this interaction, two things will happen. First ActiveInteraction will type check your inputs. Then ActiveModel will...

I think this would be nice to have. I could extract the stuff in Blunt out to a separate library as a proof of concept.

I haven't tested it yet, but I was thinking something like this: https://gist.github.com/tfausak/ff1a59b91ba540912fa90cd71bf5f76b The unsafe IORefs are a problem. Without being able to hang extra information on the `Store`, I...

That approach does look nice. I think my use cases would be covered by that. But why don't you want to allow non-namespaced dynamic metrics?

I don't have any answers for you, but check out this package for multidimensional metrics: https://github.com/sellerlabs/monad-metrics