Re: [ANN] Clojure 1.9.0-alpha5

2016-07-15 Thread Howard M. Lewis Ship
I hit this too and after an embarrasingly long time, found out the `lein clean` took care of it; I had some previously AOTed code lying around in target. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-13 Thread Jason Wolfe
The warning should be fixed in schema 1.1.2. -Jason On Monday, June 13, 2016 at 10:46:09 AM UTC+8, Josh Tilles wrote: > > On Sunday, June 12, 2016 at 10:29:56 PM UTC-4, Alan Thompson wrote: >> >> I would have expected the namespaces to avoid this kind of conflict. Why >> don't they? >> > >

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-12 Thread James Reeves
On 13 June 2016 at 03:29, Alan Thompson wrote: > I would have expected the namespaces to avoid this kind of conflict. Why > don't they? > All the vars in the clojure.core namespace are automatically imported into a namespace when it's created. It's why you can write (+ 1 1)

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-12 Thread Josh Tilles
On Sunday, June 12, 2016 at 10:29:56 PM UTC-4, Alan Thompson wrote: > > I would have expected the namespaces to avoid this kind of conflict. Why > don't they? > Because the conflict was only introduced five days ago, with this commit

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-12 Thread Alan Thompson
I would have expected the namespaces to avoid this kind of conflict. Why don't they? Alan On Sun, Jun 12, 2016 at 6:29 PM, James Reeves wrote: > On 13 June 2016 at 01:21, Alan Thompson wrote: > >> I am also getting a conflict with Plumatic Schema: >>

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-12 Thread James Reeves
On 13 June 2016 at 01:21, Alan Thompson wrote: > I am also getting a conflict with Plumatic Schema: > > WARNING: Inst already refers to: #'clojure.core/Inst in namespace: > schema.core, being replaced by: #'schema.core/Inst > > > I can't seem to find a reason for this

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-12 Thread Alan Thompson
I am also getting a conflict with Plumatic Schema: WARNING: Inst already refers to: #'clojure.core/Inst in namespace: schema.core, being replaced by: #'schema.core/Inst I can't seem to find a reason for this warning, as I don't use Inst anywhere and always say (require [schema.core :as s]

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-12 Thread Alan Thompson
On Thursday, June 9, 2016 at 11:40:03 PM UTC-7, Rangel Spasov wrote: > > Add the latest tools.analyzer as a dependency solved the problem. > > [org.clojure/tools.analyzer "0.6.9"] > >> >> I had the same problem and had to add this dependency. Is this expected? Using lein-collisions found no

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-10 Thread Rangel Spasov
Add the latest tools.analyzer as a dependency solved the problem. [org.clojure/tools.analyzer "0.6.9"] Thanks guys! On Thursday, June 9, 2016 at 6:40:12 AM UTC-7, Nicola Mometto wrote: > > I commented about this in the #clojure-dev slack channel, I believe >

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-09 Thread Sean Corfield
On 6/9/16, 6:39 AM, "Nicola Mometto" wrote: > I commented about this in the #clojure-dev slack channel, I believe > http://dev.clojure.org/jira/browse/CLJ-1874 to be the cause of this issue Interesting. I didn’t have any AOT-compiled

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-09 Thread Herwig Hochleitner
2016-06-09 15:32 GMT+02:00 Alex Miller : > > "lein deps :tree" is a good place to start, but it doesn't tell you what's > actually inside the jars. There used to be a Maven plugin that would track > down multiple class definitions across the dependency classpath, can't >

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-09 Thread Fluid Dynamics
On Thursday, June 9, 2016 at 9:32:51 AM UTC-4, Alex Miller wrote: > > I think it's quite likely that you have multiple copies of tools.analyzer > (and possibly other libs) on your classpath. Can you take a look at your > deps and see if that might be the case? > > A particular thing to watch for

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-09 Thread Nicola Mometto
I commented about this in the #clojure-dev slack channel, I believe http://dev.clojure.org/jira/browse/CLJ-1874 to be the cause of this issue > On 9 Jun 2016, at 14:32, Alex Miller wrote: > > I think it's quite likely that you have multiple copies of tools.analyzer >

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-09 Thread Alex Miller
On Wednesday, June 8, 2016 at 3:23:51 AM UTC-5, Mamun wrote: > > Excellent set of new predicates. What about date predicate? > > It would be nice if there are also date predicate as an example in bellow > > date? > Use clojure.core/inst? > date-past? > date-future? > You can use the new

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-09 Thread Alex Miller
Whoops. That is an oversight. On Wednesday, June 8, 2016 at 11:34:13 AM UTC-5, David Powell wrote: > > > Do uri? and bytes? really have generator support implemented? I couldn't > seem to get that to work. > > -- You received this message because you are subscribed to the Google Groups

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-09 Thread Alex Miller
The use of named? inside spec will be replaced with ident?. On Wednesday, June 8, 2016 at 3:13:12 PM UTC-5, Devin Walters (devn) wrote: > > Any chance of `named?` making the cut in 1.9? I see it's used in the > implementation of clojure.spec. > > -- You received this message because you are

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-09 Thread Alex Miller
I think it's quite likely that you have multiple copies of tools.analyzer (and possibly other libs) on your classpath. Can you take a look at your deps and see if that might be the case? A particular thing to watch for is if any dep is AOT compiled and transitively pulled in a dependency lib

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-08 Thread Rangel Spasov
Sean - thanks for the detailed explanation. I will try to investigate if nobody has any other ideas. On Wednesday, June 8, 2016 at 4:15:05 PM UTC-7, Sean Corfield wrote: > > I ran into this same problem with Encore but found it very, very hard to > repro in a simple project. > > > > The

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-08 Thread Sean Corfield
I ran into this same problem with Encore but found it very, very hard to repro in a simple project. The underlying issue is that clojure.tools.analyzer.utils defines boolean? but doesn’t exclude core’s version (since it’s new in Alpha 5 and libraries haven’t caught up). That normally

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-08 Thread Rangel Spasov
Hey guys - getting this compiler exception when I tried alpha 5 (up to alpha 4 it was all good). WARNING: boolean? already refers to: #'clojure.core/boolean? in namespace: clojure.tools.analyzer.utils, being replaced by: #'clojure.tools.analyzer.utils/boolean? WARNING: boolean? already refers

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-08 Thread Sean Corfield
But named? to mean instance? clojure.lang.Named tells you that something implements the Named interface which has getName() *and* getNamespace() methods – and the namespace function does *not* accept a String. The fact that the name function accepts something that is not Named is a bit of

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-08 Thread Josh Tilles
Well, it’s worth noting that clojure.core/name does account for strings : (defn name "Returns the name String of a string, symbol or keyword." {:tag String :added "1.0" :static true}

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-08 Thread Devin Walters (devn)
Any chance of `named?` making the cut in 1.9? I see it's used in the implementation of clojure.spec. On Tuesday, June 7, 2016 at 12:38:34 PM UTC-5, Alex Miller wrote: > > Clojure 1.9.0-alpha5 is now available. > > Try it via > > - Download: >

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-08 Thread David Powell
Do uri? and bytes? really have generator support implemented? I couldn't seem to get that to work. -- 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 posts from new members are

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-08 Thread Alex Miller
t;> our 30k+ lines of code where we can use bigdec? And there is also precisely >>> one place we could use biginteger?  >>> >>> >>> >>> Sean Corfield -- (904) 302-SEAN >>> An Architect's View -- http://corfield.org >>> >

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-08 Thread Remo Koch
ld -- (904) 302-SEAN >> An Architect's View -- http://corfield.org >> >> >> >> *From: *Alex Miller >> *Sent: *Tuesday, June 7, 2016 7:56 PM >> *To: *Clojure >> *Subject: *Re: [ANN] Clojure 1.9.0-alpha5 >> >> >> >> Not sure

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-08 Thread Mamun
Excellent set of new predicates. What about date predicate? It would be nice if there are also date predicate as an example in bellow date? date-past? date-future? Br, Mamun On Tuesday, June 7, 2016 at 7:38:34 PM UTC+2, Alex Miller wrote: > > Clojure 1.9.0-alpha5 is now available. > >

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-08 Thread Shantanu Kumar
On Wednesday, 8 June 2016 00:31:41 UTC+5:30, Alex Miller wrote: > > I'm not opposed to it but can't say that's anywhere on my priority list. > Does anyone use incubator? > Just to add a data point, I use incubator at work for `dissoc-in`. Shantanu > > > On Tuesday, June 7, 2016 at 1:21:34

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-07 Thread Mark Engelberg
ojure <clojure@googlegroups.com> > *Subject: *Re: [ANN] Clojure 1.9.0-alpha5 > > > > Not sure, I can ask. I think BigDecimal is probably used way more than > BigInteger. > > > On Tuesday, June 7, 2016 at 8:52:36 PM UTC-5, Sean Corfield wrote: > > Whilst u

RE: [ANN] Clojure 1.9.0-alpha5

2016-06-07 Thread sean
As a completely non-scientific data point, we had precisely one place in our 30k+ lines of code where we can use bigdec? And there is also precisely one place we could use biginteger?  Sean Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org From: Alex Miller -- You

RE: [ANN] Clojure 1.9.0-alpha5

2016-06-07 Thread sean
Thanks Alex. Based on what crossclj.info shows, I suspect you may be right that almost no one cares  https://crossclj.info/fun/clojure.core.incubator/seqable?.html Sean Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org From: Alex Miller -- You received this message

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-07 Thread Alex Miller
I don't know that anyone cares much, but I have done a new release of core.incubator (0.1.4) and deprecated seqable?. On Tuesday, June 7, 2016 at 1:21:34 PM UTC-5, Sean Corfield wrote: > > An excellent set of new predicates – thank you! > > > > Will clojure.core.incubator get a new release to

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-07 Thread Alex Miller
Not sure, I can ask. I think BigDecimal is probably used way more than BigInteger. On Tuesday, June 7, 2016 at 8:52:36 PM UTC-5, Sean Corfield wrote: > > Whilst updating our code, I noticed there’s bigdec? to test for > java.math.BigDecimal but not bigint? or biginteger? > > > > Is there a

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-07 Thread Sean Corfield
Whilst updating our code, I noticed there’s bigdec? to test for java.math.BigDecimal but not bigint? or biginteger? Is there a specific reason for that omission or were those just missed? Sean Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-07 Thread Sean Corfield
The taoensso.encore issue has defeated my attempts so far to create a repro case. Kevin Downey also confirmed that the straightforward cases of using Encore with 1.9.0 Alpha 5 all seem to work. I worked around the issue so we can continue testing Alpha 5 at World Singles (lifting a defn out of

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-07 Thread Sean Corfield
I ran across it because CongoMongo uses it and we use that. It’s not a big deal. Taoensso.encore is more problematic since that is essentially broken by the addition of bytes? to clojure.core. Right now that’s blocking us from upgrading but I haven’t established a workaround yet (technically

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-07 Thread Andy Fingerhut
crossclj.info lists 63 projects with core.incubator as a dependency. Not sure how widely used those projects are themselves: https://crossclj.info/ns/org.clojure/core.incubator/0.1.3/project.clj.html Andy On Tue, Jun 7, 2016 at 12:01 PM, Alex Miller wrote: > I'm not

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-07 Thread David Chelimsky
Pedestal: https://github.com/pedestal/pedestal/blob/master/service/project.clj#L26 On Tuesday, June 7, 2016 at 2:01:41 PM UTC-5, Alex Miller wrote: > > I'm not opposed to it but can't say that's anywhere on my priority list. > Does anyone use incubator? > > > On Tuesday, June 7, 2016 at 1:21:34

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-07 Thread Alex Miller
I'm not opposed to it but can't say that's anywhere on my priority list. Does anyone use incubator? On Tuesday, June 7, 2016 at 1:21:34 PM UTC-5, Sean Corfield wrote: > > An excellent set of new predicates – thank you! > > > > Will clojure.core.incubator get a new release to reflect that

Re: [ANN] Clojure 1.9.0-alpha5

2016-06-07 Thread Sean Corfield
An excellent set of new predicates – thank you! Will clojure.core.incubator get a new release to reflect that seqable? is available in core? WARNING: seqable? already refers to: #'clojure.core/seqable? in namespace: clojure.core.incubator, being replaced by:

[ANN] Clojure 1.9.0-alpha5

2016-06-07 Thread Alex Miller
Clojure 1.9.0-alpha5 is now available. Try it via - Download: https://repo1.maven.org/maven2/org/clojure/clojure/1.9.0-alpha5 - Leiningen: [org.clojure/clojure "1.9.0-alpha5"] 1.9.0-alpha4 includes the following changes since