This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-17
Channels
- # adventofcode (2)
- # beginners (153)
- # cider (14)
- # clara (9)
- # cljs-dev (8)
- # cljsjs (1)
- # cljsrn (4)
- # clojure (124)
- # clojure-dev (9)
- # clojure-france (18)
- # clojure-greece (22)
- # clojure-italy (11)
- # clojure-nlp (5)
- # clojure-russia (9)
- # clojure-spec (21)
- # clojure-uk (40)
- # clojurescript (82)
- # core-async (12)
- # cursive (3)
- # data-science (2)
- # datomic (225)
- # devcards (8)
- # docs (2)
- # duct (1)
- # emacs (18)
- # figwheel (2)
- # fulcro (117)
- # graphql (13)
- # hoplon (10)
- # jobs (7)
- # jobs-discuss (7)
- # keechma (8)
- # leiningen (4)
- # off-topic (16)
- # om (2)
- # om-next (3)
- # perun (11)
- # precept (4)
- # re-frame (24)
- # reagent (2)
- # remote-jobs (8)
- # ring (2)
- # ring-swagger (9)
- # rum (42)
- # shadow-cljs (8)
- # spacemacs (3)
- # specter (7)
- # uncomplicate (10)
- # unrepl (58)
- # yada (9)
This isn’t really clojure-dev related but I’m looking for some advice if this should be considered a breaking change: https://github.com/boot-clj/boot/pull/684/commits/77f5182d5159a68a5784b5376f6281b796ccbab9
@martinklepsch are you worried about "any change whatsoever is theoretically breaking" or is there some practical expectation that you think gets broken by this change?
former, can’t think of any practical expectations
I mean unless you consider intermixed strings from printing practical that is 😄
I don't think I would call it breaking then FWIW I asked stu halloway about a much grayer issue recently and his reply was to ask whether the behavior I was changing had already been specified in docstrings
so that's how I think about it now
Thanks!
@martinklepsch we can always include it in a -SNAPSHOT
version for a while and ask folks to test it
or better -alpha