Charles Reese

A lot of my methods tend to look like: ``` def func(x): f = F() >> foo >> bar >> baz return f(x) ``` Lately, I've begun to work with...

I was able to fix by adding the following to my init. ``` (set-face-foreground 'font-lock-variable-name-face "foreground") (set-face-foreground 'flymake-errline "brightred") (set-face-foreground 'font-lock-comment-face "blue") (set-face-foreground 'font-lock-comment-delimiter-face "blue") (set-face-foreground 'isearch "brightcyan") (set-face-foreground 'font-lock-keyword-face...

I think we should promote a delete/create-again workflow instead what is proposed.

Does it matter that the map contains keys your applications doesn't need? I believe clojure.spec follows a similar philosophy here.

I'm wondering if the fixture should always delete first to ensure the right environment to test. In case where the topic didn't exist, we can just catch and keep going.

Proposed solution: - Remove `KGroupedStream groupByKey(Serialized serialized)` - Add support for `KGroupedStream groupByKey(Grouped grouped)`

I was able to get it working by borrowing from the implementation of `web3::contract::Contract::events`. I'm not sure why I wasn't able to use that method directly. Could there be a...

I tried `use web3::helpers::tests::TestTransport` but I'm getting an unresolved import error. Why doesn't this work?