Re: taking my clojure game to a higher level

You are right - right now the apps that a junior dev like me are just simple stuff like webapps, which i have tried before with Clojure (but learning about webapps, Clojure and the libraries out there all at the same time made me abandon my efforts after 2 months). I am thinking i should look

Re: taking my clojure game to a higher level

I have gotten a copy of the book and am starting to work through it - thanks. I have found https://aphyr.com/tags/Clojure a very good resource as well for more in-depth learning On Sunday, August 21, 2016 at 7:24:39 PM UTC-4, puzzler wrote: > > Sounds like you are ready for this book: > >

Re: Add :examples option to s/fdef for documentation and testing?

Hi Peter, thanks for the idea, but I don't expect that we'll add this. On Sunday, August 21, 2016 at 8:26:24 AM UTC-5, Peter Marklund wrote: > > Did you consider having examples (input-output mappings) be part of the > spec for a function, i.e. add an :examples option to the fdef macro in >

Re: Two suggestions re: core.spec, `ns`, and clojure 1.9alpha11

On Sunday, August 21, 2016 at 5:28:57 PM UTC-5, lvh ‌ wrote: > > FYI, while I disagree with your conclusion (I think we should go fix > libraries instead), I ran into the same issue just now for roughly the same > reason, except the thing that pulled in an old version of core.unify was >

Re: Two suggestions re: core.spec, `ns`, and clojure 1.9alpha11

On Sunday, August 21, 2016 at 5:25:03 PM UTC-5, Brian Marick wrote: > > As an update. I’ve fixed the `ns` oopsie in Suchwow (one file), and the > coincident `ns` oopsie in Midje (one file). But this happens when running > Midje’s self-tests against Clojure 1.9alpha11: > > > Exception in

Re: taking my clojure game to a higher level

Sounds like you are ready for this book: https://www.amazon.com/Clojure-Applied-Practice-Practitioner-Vandgrift/dp/1680500740 -- 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

Re: Two suggestions re: core.spec, `ns`, and clojure 1.9alpha11

FYI, while I disagree with your conclusion (I think we should go fix libraries instead), I ran into the same issue just now for roughly the same reason, except the thing that pulled in an old version of core.unify was core.typed, which pulls in 0.5.3 through core.contracts. > On Aug 21, 2016,

Re: Two suggestions re: core.spec, `ns`, and clojure 1.9alpha11

As an update. I’ve fixed the `ns` oopsie in Suchwow (one file), and the coincident `ns` oopsie in Midje (one file). But this happens when running Midje’s self-tests against Clojure 1.9alpha11: > Exception in thread "main" java.lang.IllegalArgumentException: Call to > clojure.core/fn did not

Re: Parsing namespaced XML with clojure.data.xml

Apps are cobbled together from sub-systems and libraries. Some of those may use clojure.data.xml, either to share their products with their client or for their internal purposes. As soon as two libraries on Clojars differ in their namespace-URI to keyword-namespace mapping, has the ship sunk?

Re: taking my clojure game to a higher level

I think you just need a project to motivate you to go deeper into the language. Take on a project that you've been wanting to work on for some time and write it in Clojure. On Saturday, August 20, 2016 at 11:59:42 PM UTC-4, chia kang ren wrote: > > I started programming with Racket 2 years ago

Add :examples option to s/fdef for documentation and testing?

Did you consider having examples (input-output mappings) be part of the spec for a function, i.e. add an :examples option to the fdef macro in addition to :the current args, :ret, and :fn options? There is nothing really like examples for learning and clojuredocs.org has been immensely useful

Re: Two suggestions re: core.spec, `ns`, and clojure 1.9alpha11

The documentation now includes the spec, which would explicilly mention the symbol, so this would not be tacitly hidden as you suggest. David is already working on porting these specs to ClojureScript so that issue is one we will imminently face. So again I will state: while the current spec

Re: Parsing namespaced XML with clojure.data.xml

2016-08-20 21:43 GMT+02:00 Matching Socks : > > Could the same effect be obtained without the global state of namespace > mappings? Do all uses of clojure.data.xml in an app, even fully > encapsulated uses, have to agree about the keyword for any given well-known > XML