> On Aug 24, 2016, at 8:39 AM, Stuart Halloway <stuart.hallo...@gmail.com> > wrote: > > 3. "Follow the inverted pyramid so people see what is most important." This > kind of thing is easily done in a layer above spec, e.g. a custom REPL > printer for spec macro errors. Worth working on but not critical to getting > spec right.
So why not do it in the bottom layer? Is there some deep reason why only an unserious programmer would want information in anything other than the current clojure.spec order? (We’re talking here about reordering a list.) There has been a notable lack of “yeah, we might have made a sub-optimal decision” in this discussion. It looks bad, in my opinion. Has looked bad for a long time. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
