Upgrading a couple of projects to 1.7 seems to have gone quite smoothly.
Thanks!
However, I've encountered some problems with new features, like .cljc files.
Please see https://groups.google.com/forum/#!topic/clojure/TrYkq1lUuZw
Cheers,
Brandon
On Friday, April 24, 2015 at 11:27:34 AM UTC-7,
I am not sure why you say new primitive type hints. Primitive type hints
have been around for several Clojure released versions, 1.6.0 and earlier.
The error you are seeing is because of a property of the Clojure compiler
that as far as I know is not documented. I asked back in Nov 2014 whether
Fluid Dynamics writes:
That's weirdly inconsistent with e.g. (defn ^String prefix [s n]...).
It can be surprising behaviour, but it's not an inconsistency.
As per the documentation, metadata on the symbol being def'd *is*
evaluated, metadata on the argvec isn't.
Evaluating `String` produces
Alex Miller writes:
On Fri, May 1, 2015 at 2:53 PM, Nicola Mometto brobro...@gmail.com wrote:
Now, if you want to argue that the compiler should immediately throw an
error as soon as the wrong type hint is used rather than silently ignore
it and fail when the type-hinted form is used, I'll
On Fri, May 1, 2015 at 2:53 PM, Nicola Mometto brobro...@gmail.com wrote:
Now, if you want to argue that the compiler should immediately throw an
error as soon as the wrong type hint is used rather than silently ignore
it and fail when the type-hinted form is used, I'll agree with you and
On Friday, May 1, 2015 at 3:54:08 PM UTC-4, Nicola Mometto wrote:
Fluid Dynamics writes:
That's weirdly inconsistent with e.g. (defn ^String prefix [s n]...).
It can be surprising behaviour, but it's not an inconsistency.
As per the documentation, metadata on the symbol being def'd
I tried playing around with the new primitive type hints and got the
following weird behavior on [org.clojure/clojure 1.7.0-beta2]:
(defn ^longs init-state [] (long-array 1))
(defn ^long store-state [^longs c ^long a] (aset c 0 a))
running the following line resulted in an exception:
(let [x
Right you are, silly me :)
thanks!
On Friday, May 1, 2015 at 11:17:42 AM UTC-7, Nicola Mometto wrote:
The type-hint on init-state is wrong.
It has to be either
(defn {:tag 'longs} init-state [] (long-array 1))
or (preferred)
(defn init-state ^longs [] (long-array 1))
The type-hint on init-state is wrong.
It has to be either
(defn {:tag 'longs} init-state [] (long-array 1))
or (preferred)
(defn init-state ^longs [] (long-array 1))
shlomivak...@gmail.com writes:
I tried playing around with the new primitive type hints and got the
following weird behavior
On Friday, May 1, 2015 at 2:17:42 PM UTC-4, Nicola Mometto wrote:
The type-hint on init-state is wrong.
It has to be either
(defn {:tag 'longs} init-state [] (long-array 1))
or (preferred)
(defn init-state ^longs [] (long-array 1))
That's weirdly inconsistent with e.g. (defn
Clojure 1.7.0-beta2 is now available.
Try it via
- Download: https://repo1.maven.org/maven2/org/clojure/clojure/1.7.0-beta2/
- Leiningen: [org.clojure/clojure 1.7.0-beta2]
Regression fixes since 1.7.0-beta1:
1) CLJ-1711 - structmap iterator broken
2) CLJ-1709 - range wrong for step != 1
3)
Awesome. Just tested it on our API and working well. Looking forward to a
more in depth testing session!
- Matt
On Friday, April 24, 2015 at 2:27:40 PM UTC-4, Alex Miller wrote:
Clojure 1.7.0-beta2 is now available.
Try it via
- Download:
Thanks David!
Instaparse was using some internals of the reader, which changed for reader
conditionals, but has subsequently been patched.
On Friday, April 24, 2015 at 2:06:01 PM UTC-5, David McNeil wrote:
I did a real quick test on one of our projects. I had to upgrade to the
latest
I did a real quick test on one of our projects. I had to upgrade to the
latest compojure (seems the old version used a version of instaparse that
wouldn't compile) but after that it seemed to work and was noticably faster.
-David
--
You received this message because you are subscribed to the
14 matches
Mail list logo
