Global Spaces
-
Herwig Hochleitner
-
Re: Feature Expressions commented May 11, 2013
if any recursive call to read can (some how?) returning multiple values I think the entire reader would be much more com...
-
-
-
-
-
Kevin Downey
-
Re: Feature Expressions commented May 09, 2013
syntax quote at least can limit the scope of splicing and unsplicing to syntax quoted forms. if any recursive call to re...
-
-
Brandon Bloom
-
Re: Feature Expressions commented May 09, 2013
Oh, I though you were asking with respect to Herwig's comment. Doesn't syntax quote already have this problem? Try ` for...
-
-
Kevin Downey
-
Re: Feature Expressions commented May 09, 2013
pushing conditionals in to the reader does not save us from requiring the code to be readable on all platforms. it has t...
-
Re: Feature Expressions commented May 09, 2013
the top level is the easiest case though, the gnarly cases are splicing in to nested data structures, that may be splice...
-
-
Brandon Bloom
-
Re: Feature Expressions commented May 09, 2013
I guess at the top level, a splice would just assume an implicit "do".
-
-
Sean Corfield
-
Where Did Clojure.Contrib Go updated May 08, 2013 (view change)
Added build and JIRA links for rrbvector
-
Kevin Downey
-
Re: Feature Expressions commented May 08, 2013
have you looked at what it would take to allow the reader to splice in forms at any point? with syntax quote it is a lit...
-
-
-
Herwig Hochleitner
-
Re: Feature Expressions commented May 06, 2013
I love the consistency and minimalism of this approach. One Issue however: It probably won't be possible to readsplice o...
-
Kevin Downey
-
Re: Async blocks commented May 06, 2013
corefutures is very cool as is. It doesn't seem like try/catch/finally should be too hard to add, but I do thing it woul...
-
-
-
-
Herwig Hochleitner
-
Re: specify i.e. reify for instances commented May 06, 2013
Again, thanks for the input. I'd have completely missed the advanced compilation issue. I've updated the page with issue...
-
-
David Nolen
-
Re: specify i.e. reify for instances commented May 05, 2013
One thing that you haven't brought up is how this will interact with advanced compilation? Closure won't know anything a...
-
Re: specify i.e. reify for instances commented May 05, 2013
I see no good justification for explicit arities, it will be more work to implement yes. But specify! and specify are bo...
-
-
Herwig Hochleitner
-
Re: specify i.e. reify for instances commented May 05, 2013
My actual train of thought for the arities was: One fn per arity is always generated by the compiler protocol calls are...
-
-
David Nolen
-
Re: specify i.e. reify for instances commented May 04, 2013
Why not `specify` and `specify!` one which clones its target and one which does not. `specify` does mean that we'll like...
-
Re: specify i.e. reify for instances commented May 04, 2013
Here's benchmark illustrating an approach that caches the fns on the namespace and add locals as a property to avoid the...
-
-
-
-
Narciso L. Relata, Jr.
-
Re: Home commented Apr 29, 2013
Hello everyone. Im new in clojure programming. I want to learn from this dialect of LISP and enjoy it. thanks
-
Home created Apr 29, 2013
-
Narciso L. Relata, Jr. contributed Apr 29, 2013
-