Fork me on GitHub
#unrepl
<
2018-03-28
>
pesterhazy11:03:24

Not yet, which section in particular?

cgrand12:03:15

the growing sentiment on error reporting is relevant to this channel

dominicm12:03:18

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

pesterhazy12:03:01

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

pesterhazy12:03:46

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

pesterhazy12:03:27

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

dominicm12:03:36

It was in his talk about REPL driven development @cgrand

dominicm12:03:31

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.

cgrand12:03:40

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

cgrand12:03:40

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