[ANN] Clojure 1.10.0-beta7

Discussion:

Alex Miller

2018-11-19 21:34:03 UTC

1.10.0-beta7 is now available.

You can try it with clj using:

clj -Sdeps '{:deps {org.clojure/clojure {:mvn/version "1.10.0-beta7"}}}'

Changes in 1.10.0-beta7:

- CLJ-2435 <https://dev.clojure.org/jira/browse/CLJ-2435> - include root
cause class name in compilation and macroexpansion errors

You can read the full 1.10 changelog here:
https://github.com/clojure/clojure/blob/master/changes.md
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to ***@googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+***@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Alex Miller

2018-11-19 21:51:50 UTC

Permalink

We expect to move back into release candidates next, so testing welcome...

Post by Alex Miller
1.10.0-beta7 is now available.
clj -Sdeps '{:deps {org.clojure/clojure {:mvn/version "1.10.0-beta7"}}}'
- CLJ-2435 <https://dev.clojure.org/jira/browse/CLJ-2435> - include
root cause class name in compilation and macroexpansion errors
https://github.com/clojure/clojure/blob/master/changes.md

--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to ***@googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+***@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Andy Fingerhut

2018-11-20 04:35:24 UTC

Permalink

Not testing results this time, but just a comparison of reflection warnings
in Clojure 1.9.0 vs. 1.10.0-beta7, after adding (set! *warn-on-reflection*
true) to all .clj files in Clojure's source code that did not already have
one. These were obtained when compiling Clojure using mvn and Oracle Java
1.8.0_192.

A few reflection warnings in clojure/main.clj that were in 1.9.0 are gone
now. Cool.

One new reflection warning in Clojure 1.10.0-beta7 that was not in Clojure
1.9.0:
[java] Reflection warning, clojure/reflect/java.clj:183:35 - reference
to field getModifiers on java.lang.Object can't be resolved.

That is line 181 in the original source file here:
https://github.com/clojure/clojure/blob/master/src/clj/clojure/reflect/java.clj#L181

That code doesn't appear to have changed, so only reason I can think of off
the top of my head why a new reflection warning is perhaps due to a change
in the method resolution code?

Andy

Post by Alex Miller
We expect to move back into release candidates next, so testing welcome...

--
You received this message because you are subscribed to the Google Groups "Clojure" group.
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

Alex Miller

2018-11-20 14:48:15 UTC

Permalink

That is new code in reflect.java so that's a good catch. Patched
in https://dev.clojure.org/jira/browse/CLJ-2436 and will prob get that in
next.

Post by Andy Fingerhut
Not testing results this time, but just a comparison of reflection
warnings in Clojure 1.9.0 vs. 1.10.0-beta7, after adding (set!
*warn-on-reflection* true) to all .clj files in Clojure's source code that
did not already have one. These were obtained when compiling Clojure using
mvn and Oracle Java 1.8.0_192.
A few reflection warnings in clojure/main.clj that were in 1.9.0 are gone
now. Cool.
One new reflection warning in Clojure 1.10.0-beta7 that was not in Clojure
[java] Reflection warning, clojure/reflect/java.clj:183:35 -
reference to field getModifiers on java.lang.Object can't be resolved.
https://github.com/clojure/clojure/blob/master/src/clj/clojure/reflect/java.clj#L181
That code doesn't appear to have changed, so only reason I can think of
off the top of my head why a new reflection warning is perhaps due to a
change in the method resolution code?
Andy

Sean Corfield

2018-11-20 17:39:06 UTC

Permalink

Given how small the delta is from Beta 6 to Beta 7, it should surprise no one that all our tests pass on Beta 7 at World Singles Networks ð

Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
An Architect's View -- http://corfield.org/

"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood

________________________________
From: ***@googlegroups.com <***@googlegroups.com> on behalf of Alex Miller <***@puredanger.com>
Sent: Monday, November 19, 2018 1:34:03 PM
To: Clojure
Subject: [ANN] Clojure 1.10.0-beta7

1.10.0-beta7 is now available.

You can try it with clj using:

clj -Sdeps '{:deps {org.clojure/clojure {:mvn/version "1.10.0-beta7"}}}'

Changes in 1.10.0-beta7:

* CLJ-2435<https://dev.clojure.org/jira/browse/CLJ-2435> - include root cause class name in compilation and macroexpansion errors

You can read the full 1.10 changelog here: https://github.com/clojure/clojure/blob/master/changes.md

--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to ***@googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+***@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure+***@googlegroups.com<mailto:clojure+***@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to ***@googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+***@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Matching Socks

2018-11-20 23:50:13 UTC

Permalink

For those keeping score at home, the CLJ-2436 patch says,

(defn- typeref->class
- [typeref classloader]
+ ^Class [typeref classloader]
(if (class? typeref)
typeref
- (clojure.lang.RT/classForName (typename typeref) false classloader)))
+ (clojure.lang.RT/classForName (typename typeref) false classloader)))

I was wondering why the compiler required the type hint. It reminded me of
something I had seen in the news recently, regarding ClojureScript. The
ClojureScript changes.md lists "CLJS-1997: Outward function type hint
propagation". That issue, in turn, has an informative comment (Thanks,
Mike Fikes!) about *Clojure*:

Bronsa helpfully pointed out in Slack that outward type hint propagation is
avoided in Clojure because it breaks things like:

(defn foo [] 1)
(defn bar [] (String/valueOf (foo)))
(defn foo [] "foo")
(bar)
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to ***@googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+***@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Alex Miller

2018-11-21 02:53:11 UTC

Permalink

Post by Matching Socks
For those keeping score at home, the CLJ-2436 patch says,
(defn- typeref->class
- [typeref classloader]
+ ^Class [typeref classloader]
(if (class? typeref)
typeref
- (clojure.lang.RT/classForName (typename typeref) false classloader)))
+ (clojure.lang.RT/classForName (typename typeref) false classloader)))
I was wondering why the compiler required the type hint.

Without the type hint the compiler assumes the return type of
typeref->class is Object. Later code that uses that return value does Java
interop and so it was reflecting. Adding the type hint is sufficient to
tell the consumer what it's returning.

Post by Matching Socks
It reminded me of something I had seen in the news recently, regarding
ClojureScript. The ClojureScript changes.md lists "CLJS-1997: Outward
function type hint propagation". That issue, in turn, has an informative
Bronsa helpfully pointed out in Slack that outward type hint propagation
(defn foo [] 1)
(defn bar [] (String/valueOf (foo)))
(defn foo [] "foo")
(bar)