I do not practice TDD a lot, but I think that thanks to recent events clojurescript will attract people more sensible to TDD workflows.
Due to a limitation of austin and clojurescript.test regarding :none optimisation, it's not possible to use it with them. So we have to switch to :whitespace (or one of the others). But if we use :whitespace (or one of the others optimisation options) its compilation/recompilation time it's very slow compared to :none when paired with :source-map. By renouncing to :source-map option, the :whitespace compilation/re-compilation time is very fast again. The question for TDD practitioners is the following: How fundamental is the availability of cljs's source-map in a TDD workflow? Could we renounce to it in favour of a quicker TDD loop? Do you see any drawback in a TDD scenario for not having the source-map? Honestly, I use source-map rarely (never in a TDD workflow) and only for debugging purpose because it allows me to set breakpoints and inspect bindings. It seems to me that renouncing to source-map in a TDD workflow is not a big deal. Am I correct? Thanks Mimmo
signature.asc
Description: Message signed with OpenPGP using GPGMail
