unrepl 2018-03-28

Not yet, which section in particular?

the growing sentiment on error reporting is relevant to this channel

I think Stu really nailed it, you need the form and the exception to do anything useful about messages

Yeah it's interesting how error messages are perceived as a regression from 1.8

I feel like unravel and other unrepl clients could really help here by giving collapsed-by-default expandable errors

The nitty gritty detail (deep stacktraces, complete spec errors) is hidden by default but it's all there if you need it

It was in his talk about REPL driven development @cgrand

I've never understood stack trace woes, they make a lot of sense to me. But spec errors are opaque to me. I've no idea how to solve that even for my environment.

Traditional stack traces are noisy/verbose but makes sense (except for the occasional lazy sequences putting the blame on the consumer)

@matttylr has left the channel