Ben Brinckerhoff
Ben Brinckerhoff
Awesome video! I hadn't seen that one yet, but it really does show off the power of REPL-driven-development. I agree that using the REPL to reload the code via `(require...
@mfikes It's a _great_ tool and I'm more than happy to help smooth out those corners :smile:. Unfortunately, I don't yet see the root cause (sorry, my objective-c is weak),...
I’m on vacation without my laptop so I can’t look at this in detail right now, but off the top of my head, I don’t think this would break expound...
I had forgotten that expound already prints out the function arguments if the `:fn` spec is not satisfied, e.g.: ``` -- Spec failed -------------------- Function arguments and return value {:ret...
I was hoping the ["Improved Exception Messages and Printing" fixes](https://clojurescript.org/news/2019-01-31-release#_clojure_1_10_features) would fix compatibilities with Expound, but my initial testing indicates that this is only partially fixed. I'll have more time...
Something like https://dev.clojure.org/jira/browse/CLJS-2913 ? ;)
But yes, I will make a follow up JIRA once I have isolated a minimal repro 😄
@arichiardi There are a lot of moving parts here. Can you post a repro including CLJS version, CLJ version, spec version, and if you are calling a function or a...
https://dev.clojure.org/jira/browse/CLJS-3050
> You could submit Orchestra and Expound to https://github.com/cljs-oss/canary so it will be tested automatically and thoroughly. This is a good idea in general, but wouldn't have caught the particular...