Re: Help ship Clojure 1.9!

[Alan Thompson]

Before Clojure 1.9 is shipped, I would like to reiterate the appeal from
many in the community to stop the terrible, permanent mistake that is
*clojure.core/any?*

For those who have not seen past emails on this topic, you may view the
main threads here:

   -
   
https://groups.google.com/forum/#!searchin/clojure/semantic$20mismatch$20any%7Csort:relevance/clojure/f25y6N1OiIo/5Gq70PV1CAAJ
   -
   
https://groups.google.com/forum/#!searchin/clojure/any$20not-any$20mismatch%7Csort:relevance/clojure/2l2f1jKExUc/aX4KpqlABAAJ
   -
   
https://groups.google.com/forum/#!searchin/clojure/any$20not-any$20mismatch%7Csort:relevance/clojure/tPiW2DGHTN0/A4LyknV4BAAJ

Alan


On Wed, Oct 4, 2017 at 1:27 PM, Michał Marczyk 
wrote:

> I've run into a behaviour change that was actually already present in
> alpha20 – with the CLJ-99 patch in place, {min,max}-key now return the
> first argument with the minimum/maximum key, whereas previously they
> returned the last such argument.
>
> The new behaviour seems like the more natural one, but this is a breaking
> change, so I filed https://dev.clojure.org/jira/browse/CLJ-2247 to track
> this (with a patch that takes the "default" approach of restoring
> established behaviour).
>
> Cheers,
> Michał
>
>
> On 3 October 2017 at 21:11, Beau Fabry  wrote:
>
>> We've been using 1.9 in a small app for a while with no issues. After
>> upgrading schema to the latest version (with the PR above) I've also
>> successfully run our larger codebase with 1.9.
>>
>> On Tuesday, October 3, 2017 at 4:41:14 AM UTC-7, stuart@gmail.com
>> wrote:
>>>
>>> Hi Mark,
>>>
>>> I think this approach totally makes sense, and the alpha naming exists
>>> to inform this kind of decision-making.
>>>
>>> For libraries where the use of spec does not have to be user-facing, I
>>> am putting specs in separate (Clojure) namespaces, and loading them in such
>>> a way that they can coexist with non (or maybe different) spec
>>> environments. But that is extra work for sure.
>>>
>>> Stu
>>>
>>> On Mon, Oct 2, 2017 at 3:35 PM, Mark Engelberg 
>>> wrote:
>>>
 On Mon, Oct 2, 2017 at 7:55 AM, Stuart Halloway 
 wrote:

> Hi David,
>
> Spec will be in alpha for a while. That is part of the point of it
> being a separate library. Can you say more about what problems this is
> causing?
>
> Stu
>
>
 As a library maintainer, I am forced to upgrade and release my library
 any time something I depend upon makes a breaking change.  I don't get paid
 for maintaining open source libraries, it's something I do in my spare
 time, so I prefer to do it on my own schedule.  When an underlying library
 makes a breaking change, I get dozens of urgent requests from people who
 need me to cut a new release ASAP, and by Murphy's Law, that often happens
 when I have very little time to do it.  It's a nuisance.

 Clojure is pretty good about not making breaking changes, but it
 happens from time to time.  Clojurescript is less good about not making
 breaking changes, and therefore, maintaining Clojurescript libraries is
 more of a headache.  On the plus side, Clojurescript users seem to care
 very little about backwards compatibility (most keep up with the latest
 version), so sometimes it is easier to make a change to keep up with a
 change in Clojurescript than one in Clojure, where I am expected to not
 only support the latest breaking change, but also the last several 
 releases.

 Anything that is labeled as "alpha" is waving a big red flag that there
 could be breaking changes at any time with little warning.  For my
 libraries which depend on spec, there's no way I'm going to bring them out
 of alpha status until spec comes out of alpha status.  If I make an
 official release of something that depends on spec, then I'm going to be on
 the hook to rapidly cut a new release every time spec changes, which could
 be at any time.  I don't want that hassle.  I don't want to make a promise
 to the community to maintain a stable product if the thing I depend upon
 has not made a similar promise.  When spec reaches a point where the API
 will not be changing, or rather, when we know that new changes will only be
 additive, I can begin to trust that it won't be a huge maintenance headache
 to release something based on spec.

 --
 You received this message because you are subscribed to the Google
 Groups "Clojure" group.
 To post to this group, send email to clo...@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+u...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/clojure?hl=en
 ---
 You 

Re: Help ship Clojure 1.9!

[Michał Marczyk]

I've run into a behaviour change that was actually already present in
alpha20 – with the CLJ-99 patch in place, {min,max}-key now return the
first argument with the minimum/maximum key, whereas previously they
returned the last such argument.

The new behaviour seems like the more natural one, but this is a breaking
change, so I filed https://dev.clojure.org/jira/browse/CLJ-2247 to track
this (with a patch that takes the "default" approach of restoring
established behaviour).

Cheers,
Michał


On 3 October 2017 at 21:11, Beau Fabry  wrote:

> We've been using 1.9 in a small app for a while with no issues. After
> upgrading schema to the latest version (with the PR above) I've also
> successfully run our larger codebase with 1.9.
>
> On Tuesday, October 3, 2017 at 4:41:14 AM UTC-7, stuart@gmail.com
> wrote:
>>
>> Hi Mark,
>>
>> I think this approach totally makes sense, and the alpha naming exists to
>> inform this kind of decision-making.
>>
>> For libraries where the use of spec does not have to be user-facing, I am
>> putting specs in separate (Clojure) namespaces, and loading them in such a
>> way that they can coexist with non (or maybe different) spec environments.
>> But that is extra work for sure.
>>
>> Stu
>>
>> On Mon, Oct 2, 2017 at 3:35 PM, Mark Engelberg 
>> wrote:
>>
>>> On Mon, Oct 2, 2017 at 7:55 AM, Stuart Halloway 
>>> wrote:
>>>
 Hi David,

 Spec will be in alpha for a while. That is part of the point of it
 being a separate library. Can you say more about what problems this is
 causing?

 Stu


>>> As a library maintainer, I am forced to upgrade and release my library
>>> any time something I depend upon makes a breaking change.  I don't get paid
>>> for maintaining open source libraries, it's something I do in my spare
>>> time, so I prefer to do it on my own schedule.  When an underlying library
>>> makes a breaking change, I get dozens of urgent requests from people who
>>> need me to cut a new release ASAP, and by Murphy's Law, that often happens
>>> when I have very little time to do it.  It's a nuisance.
>>>
>>> Clojure is pretty good about not making breaking changes, but it happens
>>> from time to time.  Clojurescript is less good about not making breaking
>>> changes, and therefore, maintaining Clojurescript libraries is more of a
>>> headache.  On the plus side, Clojurescript users seem to care very little
>>> about backwards compatibility (most keep up with the latest version), so
>>> sometimes it is easier to make a change to keep up with a change in
>>> Clojurescript than one in Clojure, where I am expected to not only support
>>> the latest breaking change, but also the last several releases.
>>>
>>> Anything that is labeled as "alpha" is waving a big red flag that there
>>> could be breaking changes at any time with little warning.  For my
>>> libraries which depend on spec, there's no way I'm going to bring them out
>>> of alpha status until spec comes out of alpha status.  If I make an
>>> official release of something that depends on spec, then I'm going to be on
>>> the hook to rapidly cut a new release every time spec changes, which could
>>> be at any time.  I don't want that hassle.  I don't want to make a promise
>>> to the community to maintain a stable product if the thing I depend upon
>>> has not made a similar promise.  When spec reaches a point where the API
>>> will not be changing, or rather, when we know that new changes will only be
>>> additive, I can begin to trust that it won't be a huge maintenance headache
>>> to release something based on spec.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Clojure" group.
>>> To post to this group, send email to clo...@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+u...@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+u...@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 clojure@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+unsubscr...@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 

Re: Help ship Clojure 1.9!

[Beau Fabry]

We've been using 1.9 in a small app for a while with no issues. After 
upgrading schema to the latest version (with the PR above) I've also 
successfully run our larger codebase with 1.9.

On Tuesday, October 3, 2017 at 4:41:14 AM UTC-7, stuart@gmail.com wrote:
>
> Hi Mark,
>
> I think this approach totally makes sense, and the alpha naming exists to 
> inform this kind of decision-making.
>
> For libraries where the use of spec does not have to be user-facing, I am 
> putting specs in separate (Clojure) namespaces, and loading them in such a 
> way that they can coexist with non (or maybe different) spec environments. 
> But that is extra work for sure.
>
> Stu
>
> On Mon, Oct 2, 2017 at 3:35 PM, Mark Engelberg  > wrote:
>
>> On Mon, Oct 2, 2017 at 7:55 AM, Stuart Halloway > > wrote:
>>
>>> Hi David,
>>>
>>> Spec will be in alpha for a while. That is part of the point of it being 
>>> a separate library. Can you say more about what problems this is causing?
>>>
>>> Stu
>>>
>>>
>> As a library maintainer, I am forced to upgrade and release my library 
>> any time something I depend upon makes a breaking change.  I don't get paid 
>> for maintaining open source libraries, it's something I do in my spare 
>> time, so I prefer to do it on my own schedule.  When an underlying library 
>> makes a breaking change, I get dozens of urgent requests from people who 
>> need me to cut a new release ASAP, and by Murphy's Law, that often happens 
>> when I have very little time to do it.  It's a nuisance.
>>
>> Clojure is pretty good about not making breaking changes, but it happens 
>> from time to time.  Clojurescript is less good about not making breaking 
>> changes, and therefore, maintaining Clojurescript libraries is more of a 
>> headache.  On the plus side, Clojurescript users seem to care very little 
>> about backwards compatibility (most keep up with the latest version), so 
>> sometimes it is easier to make a change to keep up with a change in 
>> Clojurescript than one in Clojure, where I am expected to not only support 
>> the latest breaking change, but also the last several releases.
>>
>> Anything that is labeled as "alpha" is waving a big red flag that there 
>> could be breaking changes at any time with little warning.  For my 
>> libraries which depend on spec, there's no way I'm going to bring them out 
>> of alpha status until spec comes out of alpha status.  If I make an 
>> official release of something that depends on spec, then I'm going to be on 
>> the hook to rapidly cut a new release every time spec changes, which could 
>> be at any time.  I don't want that hassle.  I don't want to make a promise 
>> to the community to maintain a stable product if the thing I depend upon 
>> has not made a similar promise.  When spec reaches a point where the API 
>> will not be changing, or rather, when we know that new changes will only be 
>> additive, I can begin to trust that it won't be a huge maintenance headache 
>> to release something based on spec.
>>
>> -- 
>> You received this message because you are subscribed to the Google
>> Groups "Clojure" group.
>> To post to this group, send email to clo...@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+u...@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+u...@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 clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help ship Clojure 1.9!

[Stuart Halloway]

Hi Mark,

I think this approach totally makes sense, and the alpha naming exists to
inform this kind of decision-making.

For libraries where the use of spec does not have to be user-facing, I am
putting specs in separate (Clojure) namespaces, and loading them in such a
way that they can coexist with non (or maybe different) spec environments.
But that is extra work for sure.

Stu

On Mon, Oct 2, 2017 at 3:35 PM, Mark Engelberg 
wrote:

> On Mon, Oct 2, 2017 at 7:55 AM, Stuart Halloway  > wrote:
>
>> Hi David,
>>
>> Spec will be in alpha for a while. That is part of the point of it being
>> a separate library. Can you say more about what problems this is causing?
>>
>> Stu
>>
>>
> As a library maintainer, I am forced to upgrade and release my library any
> time something I depend upon makes a breaking change.  I don't get paid for
> maintaining open source libraries, it's something I do in my spare time, so
> I prefer to do it on my own schedule.  When an underlying library makes a
> breaking change, I get dozens of urgent requests from people who need me to
> cut a new release ASAP, and by Murphy's Law, that often happens when I have
> very little time to do it.  It's a nuisance.
>
> Clojure is pretty good about not making breaking changes, but it happens
> from time to time.  Clojurescript is less good about not making breaking
> changes, and therefore, maintaining Clojurescript libraries is more of a
> headache.  On the plus side, Clojurescript users seem to care very little
> about backwards compatibility (most keep up with the latest version), so
> sometimes it is easier to make a change to keep up with a change in
> Clojurescript than one in Clojure, where I am expected to not only support
> the latest breaking change, but also the last several releases.
>
> Anything that is labeled as "alpha" is waving a big red flag that there
> could be breaking changes at any time with little warning.  For my
> libraries which depend on spec, there's no way I'm going to bring them out
> of alpha status until spec comes out of alpha status.  If I make an
> official release of something that depends on spec, then I'm going to be on
> the hook to rapidly cut a new release every time spec changes, which could
> be at any time.  I don't want that hassle.  I don't want to make a promise
> to the community to maintain a stable product if the thing I depend upon
> has not made a similar promise.  When spec reaches a point where the API
> will not be changing, or rather, when we know that new changes will only be
> additive, I can begin to trust that it won't be a huge maintenance headache
> to release something based on spec.
>
> --
> 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 moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@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+unsubscr...@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 clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help ship Clojure 1.9!

[Alex Miller]

On Monday, October 2, 2017 at 3:16:55 PM UTC-5, Rob Nikander wrote:
>
> I get this when I switch from 1.8 to 1.9 beta, but maybe it's an issue 
> with the `core.match` library?
>
> WARNING: boolean? already refers to: #'clojure.core/boolean? in namespace: 
> clojure.tools.analyzer.utils, being replaced by: 
> #'clojure.tools.analyzer.utils/boolean?
>

This is fixed in the latest version of core.match (by removing the unused 
clojure.tools.analyzer ns):

[org.clojure/core.match "0.3.0-alpha5"]


 

>

-- 
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 moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help ship Clojure 1.9!

[Rob Nikander]

I get this when I switch from 1.8 to 1.9 beta, but maybe it's an issue with 
the `core.match` library?

WARNING: boolean? already refers to: #'clojure.core/boolean? in namespace: 
clojure.tools.analyzer.utils, being replaced by: 
#'clojure.tools.analyzer.utils/boolean?

Rob


On Thursday, September 28, 2017 at 10:00:16 AM UTC-4, stuart@gmail.com 
wrote:
>
> Clojure 1.9 has been quite stable throughout the alpha period, and we now 
> hope to release after a very short beta. Please test your existing programs 
> on the latest beta (see below), and respond on this thread ASAP if you 
> discover anything you believe to be a regression.
>
> Thanks!
> Stu
>

-- 
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 moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help ship Clojure 1.9!

[Mark Engelberg]

On Mon, Oct 2, 2017 at 7:55 AM, Stuart Halloway 
wrote:

> Hi David,
>
> Spec will be in alpha for a while. That is part of the point of it being a
> separate library. Can you say more about what problems this is causing?
>
> Stu
>
>
As a library maintainer, I am forced to upgrade and release my library any
time something I depend upon makes a breaking change.  I don't get paid for
maintaining open source libraries, it's something I do in my spare time, so
I prefer to do it on my own schedule.  When an underlying library makes a
breaking change, I get dozens of urgent requests from people who need me to
cut a new release ASAP, and by Murphy's Law, that often happens when I have
very little time to do it.  It's a nuisance.

Clojure is pretty good about not making breaking changes, but it happens
from time to time.  Clojurescript is less good about not making breaking
changes, and therefore, maintaining Clojurescript libraries is more of a
headache.  On the plus side, Clojurescript users seem to care very little
about backwards compatibility (most keep up with the latest version), so
sometimes it is easier to make a change to keep up with a change in
Clojurescript than one in Clojure, where I am expected to not only support
the latest breaking change, but also the last several releases.

Anything that is labeled as "alpha" is waving a big red flag that there
could be breaking changes at any time with little warning.  For my
libraries which depend on spec, there's no way I'm going to bring them out
of alpha status until spec comes out of alpha status.  If I make an
official release of something that depends on spec, then I'm going to be on
the hook to rapidly cut a new release every time spec changes, which could
be at any time.  I don't want that hassle.  I don't want to make a promise
to the community to maintain a stable product if the thing I depend upon
has not made a similar promise.  When spec reaches a point where the API
will not be changing, or rather, when we know that new changes will only be
additive, I can begin to trust that it won't be a huge maintenance headache
to release something based on spec.

-- 
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 moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help ship Clojure 1.9!

[David Bürgin]

Hello Stu,

On 02/10/17 16:55, Stuart Halloway wrote:
> Spec will be in alpha for a while. That is part of the point of it being
> a separate library. Can you say more about what problems this is causing?

I don’t have any stakes in this so it’s better if I withdraw my
question.

I was (still am) a bit worried that the alpha namespaces of spec are
going to be visible for all users (tooling?) via error messages. I also
have difficulties imagining how the migration from spec.alpha to spec
will work (impacts all libraries using it?) … I may just be confused.


-- 
David

-- 
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 moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: Help ship Clojure 1.9!

[Sean Corfield]

I would perhaps prevail on those library maintainers to clarify such 
statements…?



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: clojure@googlegroups.com <clojure@googlegroups.com> on behalf of David 
Bürgin <dbuer...@gluet.ch>
Sent: Saturday, September 30, 2017 1:52:47 AM
To: clojure@googlegroups.com
Subject: Re: Help ship Clojure 1.9!

On 28/09/17 16:00, Stuart Halloway wrote:
> Clojure 1.9 has been quite stable throughout the alpha period, and we
> now hope to release after a very short beta. Please test your existing
> programs on the latest beta (see below), and respond on this thread ASAP
> if you discover anything you believe to be a regression.

Will there be a non-alpha release of spec together with Clojure 1.9?

Some newer libraries have statements like ‘in alpha while Clojure 1.9 is
in alpha’, but what they actually seem to mean is that they’re in alpha
while spec is in alpha. I think a proper release of spec (namespaces
without the word ‘alpha’) sometime soon would be very welcome.

--
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 moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@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+unsubscr...@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 clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help ship Clojure 1.9!

[Leon Grapenthin]

Since spec is mainly a dependency of 1.9. to improve error reporting over 
1.8 (correct me if I'm wrong), I'd like to point out this ticket 
again: https://dev.clojure.org/jira/browse/CLJ-2013

It solves what I determined the root cause of this report 
https://groups.google.com/d/msg/clojure/mIlKaOiujlo/6b0So2siCgAJ which 
triggered a lengthy discussion at the time.

Also, the standard error reporter should sort problems by depth (length) of 
part as a default.

Thanks for looking into it,
 Leon.

On Thursday, September 28, 2017 at 4:00:16 PM UTC+2, stuart@gmail.com 
wrote:
>
> Clojure 1.9 has been quite stable throughout the alpha period, and we now 
> hope to release after a very short beta. Please test your existing programs 
> on the latest beta (see below), and respond on this thread ASAP if you 
> discover anything you believe to be a regression.
>
> Thanks!
> Stu
>
> ;; Clojure deps.edn
> org.clojure/clojure {:mvn/version "1.9.0-beta1"}
>
> ;; lein & boot
> [org.clojure/clojure "1.9.0-beta1"]
>
>

-- 
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 moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help ship Clojure 1.9!

[Stuart Halloway]

Hi David,

Spec will be in alpha for a while. That is part of the point of it being a
separate library. Can you say more about what problems this is causing?

Stu

On Sat, Sep 30, 2017 at 4:52 AM, David Bürgin  wrote:

> On 28/09/17 16:00, Stuart Halloway wrote:
> > Clojure 1.9 has been quite stable throughout the alpha period, and we
> > now hope to release after a very short beta. Please test your existing
> > programs on the latest beta (see below), and respond on this thread ASAP
> > if you discover anything you believe to be a regression.
>
> Will there be a non-alpha release of spec together with Clojure 1.9?
>
> Some newer libraries have statements like ‘in alpha while Clojure 1.9 is
> in alpha’, but what they actually seem to mean is that they’re in alpha
> while spec is in alpha. I think a proper release of spec (namespaces
> without the word ‘alpha’) sometime soon would be very welcome.
>
> --
> 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 moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@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+unsubscr...@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 clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help ship Clojure 1.9!

[Borkdude]

Other than spotting an issue with yada which involved upgrading aleph 
(https://github.com/juxt/yada/issues/199) and an issue with ClojureScript 
with was fixed on master I haven't encountered any problems. All our 
integration tests pass. Good luck with bringing Clojure 1.9.0 out the door!

On Thursday, September 28, 2017 at 4:00:16 PM UTC+2, stuart@gmail.com 
wrote:
>
> Clojure 1.9 has been quite stable throughout the alpha period, and we now 
> hope to release after a very short beta. Please test your existing programs 
> on the latest beta (see below), and respond on this thread ASAP if you 
> discover anything you believe to be a regression.
>
> Thanks!
> Stu
>
> ;; Clojure deps.edn
> org.clojure/clojure {:mvn/version "1.9.0-beta1"}
>
> ;; lein & boot
> [org.clojure/clojure "1.9.0-beta1"]
>
>

-- 
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 moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help ship Clojure 1.9!

[David Bürgin]

On 28/09/17 16:00, Stuart Halloway wrote:
> Clojure 1.9 has been quite stable throughout the alpha period, and we
> now hope to release after a very short beta. Please test your existing
> programs on the latest beta (see below), and respond on this thread ASAP
> if you discover anything you believe to be a regression.

Will there be a non-alpha release of spec together with Clojure 1.9?

Some newer libraries have statements like ‘in alpha while Clojure 1.9 is
in alpha’, but what they actually seem to mean is that they’re in alpha
while spec is in alpha. I think a proper release of spec (namespaces
without the word ‘alpha’) sometime soon would be very welcome.

-- 
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 moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help ship Clojure 1.9!

[Nicola Mometto]

Yes, clojurescript makes use of a previous experimental feature of 
tools.reader that allowed Infinity and -Infinity to be read as 
Double/POSITIVE_INFINITY and Double/NEGATIVE_INFINITY, without special 
casing how the compiler emitted infinity literals, as clojure previously 
printed them as "Infinity" and "-Infinity" which is the valid javascript 
code. Now that clojure has changed how infinities are printed, 
clojurescript broke and the compiler now explicitely has to handle how 
infinities are printed, rather than simply using the pr-str 
representation of numbers.



On 29/09/17 19:47, Stuart Halloway wrote:
And to maybe answer my own question, I guess it is 
https://github.com/clojure/clojurescript/blob/master/src/main/cljs/cljs/core.cljs#L988-L990.


On Fri, Sep 29, 2017 at 1:45 PM, Stuart Halloway 
> wrote:


To be clear: we can certainly cut a new release of CLJS, I just
want to understand other options, if any.

On Fri, Sep 29, 2017 at 1:38 PM, Stuart Halloway
> wrote:

Hi Aleš, Mark,

Thanks for the reports! It isn't clear to me how a change to
tools.reader can fix a problem with the core hash function.
Can somebody point me to the place in the Clojurescript code
where this happens?

Stu

On Fri, Sep 29, 2017 at 11:13 AM, Aleš Roubíček
> wrote:

The Cljs problem is easily solvable by referencing latest
tools.reader:

[org.clojure/clojurescript "1.9.908" :exclusions
[org.clojure/tools.reader]] [org.clojure/tools.reader "1.1.0"]


On Thursday, September 28, 2017 at 8:37:11 PM UTC+2,
puzzler wrote:

And to be clear, it doesn't only affect people who try
to use ##Inf or ##NaN in their Clojurescript code. It
affects all existing Clojurescript code, because
running the Clojurescript compiler in a new version of
Clojure causes all Clojurescript code to emit these ##
characters directly into the javascript for its
definition of the core hash function, which is
nonsensical javascript.  So all Clojurescript code is
broken by running the new release.

On Thu, Sep 28, 2017 at 11:34 AM, Mark Engelberg
 wrote:

On Thu, Sep 28, 2017 at 11:02 AM, Jeaye
 wrote:

This has been the only issue we've run into
with 1.9.0-beta1 ( ticket is here
https://dev.clojure.org/jira/browse/CLJS-2352

). On our back-end, all tests are good, but we
can't currently use beta1 (or alpha20) on the
front-end, since this issue causes CLJS to
choke. I'm hoping that a new version of CLJS
comes out before Clojure 1.9.0 so that people
don't get the false impression that the latest
of each is compatible with the other.

J


Agreed.  It is currently not possible to use
Clojure 1.9.0 later than alpha19 with
Clojurescript. Clojurescript as it currently
stands can't handle the new ## tags like ##Inf,
##NaN.  Like a number of people, I got burned by
this when I tried to upgrade and spent some time
tracking it down, only to realize it was already a
known incompatibility. There will be a lot more
confused people if you release Clojure 1.9.0 prior
to releasing a new version of Clojurescript that
is compatible.


-- 
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 moderated - please be
patient with your first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@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.
 

Re: Help ship Clojure 1.9!

[Stuart Halloway]

And to maybe answer my own question, I guess it is
https://github.com/clojure/clojurescript/blob/master/src/main/cljs/cljs/core.cljs#L988-L990
.

On Fri, Sep 29, 2017 at 1:45 PM, Stuart Halloway 
wrote:

> To be clear: we can certainly cut a new release of CLJS, I just want to
> understand other options, if any.
>
> On Fri, Sep 29, 2017 at 1:38 PM, Stuart Halloway <
> stuart.hallo...@gmail.com> wrote:
>
>> Hi Aleš, Mark,
>>
>> Thanks for the reports! It isn't clear to me how a change to tools.reader
>> can fix a problem with the core hash function. Can somebody point me to the
>> place in the Clojurescript code where this happens?
>>
>> Stu
>>
>> On Fri, Sep 29, 2017 at 11:13 AM, Aleš Roubíček  wrote:
>>
>>> The Cljs problem is easily solvable by referencing latest tools.reader:
>>>
>>>  [org.clojure/clojurescript "1.9.908" :exclusions 
>>> [org.clojure/tools.reader]]
>>>  [org.clojure/tools.reader "1.1.0"]
>>>
>>>
>>>
>>>
>>> On Thursday, September 28, 2017 at 8:37:11 PM UTC+2, puzzler wrote:

 And to be clear, it doesn't only affect people who try to use ##Inf or
 ##NaN in their Clojurescript code.  It affects all existing Clojurescript
 code, because running the Clojurescript compiler in a new version of
 Clojure causes all Clojurescript code to emit these ## characters directly
 into the javascript for its definition of the core hash function, which is
 nonsensical javascript.  So all Clojurescript code is broken by running the
 new release.

 On Thu, Sep 28, 2017 at 11:34 AM, Mark Engelberg 
 wrote:

> On Thu, Sep 28, 2017 at 11:02 AM, Jeaye  wrote:
>
>> This has been the only issue we've run into with 1.9.0-beta1 ( ticket
>> is here https://dev.clojure.org/jira/browse/CLJS-2352 ). On our
>> back-end, all tests are good, but we can't currently use beta1 (or 
>> alpha20)
>> on the front-end, since this issue causes CLJS to choke. I'm hoping that 
>> a
>> new version of CLJS comes out before Clojure 1.9.0 so that people don't 
>> get
>> the false impression that the latest of each is compatible with the 
>> other.
>>
>> J
>>
>>
> Agreed.  It is currently not possible to use Clojure 1.9.0 later than
> alpha19 with Clojurescript.  Clojurescript as it currently stands can't
> handle the new ## tags like ##Inf, ##NaN.  Like a number of people, I got
> burned by this when I tried to upgrade and spent some time tracking it
> down, only to realize it was already a known incompatibility.  There will
> be a lot more confused people if you release Clojure 1.9.0 prior to
> releasing a new version of Clojurescript that is compatible.
>

 --
>>> 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 moderated - please be patient with
>>> your first post.
>>> To unsubscribe from this group, send email to
>>> clojure+unsubscr...@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+unsubscr...@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 clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help ship Clojure 1.9!

[Stuart Halloway]

To be clear: we can certainly cut a new release of CLJS, I just want to
understand other options, if any.

On Fri, Sep 29, 2017 at 1:38 PM, Stuart Halloway 
wrote:

> Hi Aleš, Mark,
>
> Thanks for the reports! It isn't clear to me how a change to tools.reader
> can fix a problem with the core hash function. Can somebody point me to the
> place in the Clojurescript code where this happens?
>
> Stu
>
> On Fri, Sep 29, 2017 at 11:13 AM, Aleš Roubíček  wrote:
>
>> The Cljs problem is easily solvable by referencing latest tools.reader:
>>
>>  [org.clojure/clojurescript "1.9.908" :exclusions [org.clojure/tools.reader]]
>>  [org.clojure/tools.reader "1.1.0"]
>>
>>
>>
>>
>> On Thursday, September 28, 2017 at 8:37:11 PM UTC+2, puzzler wrote:
>>>
>>> And to be clear, it doesn't only affect people who try to use ##Inf or
>>> ##NaN in their Clojurescript code.  It affects all existing Clojurescript
>>> code, because running the Clojurescript compiler in a new version of
>>> Clojure causes all Clojurescript code to emit these ## characters directly
>>> into the javascript for its definition of the core hash function, which is
>>> nonsensical javascript.  So all Clojurescript code is broken by running the
>>> new release.
>>>
>>> On Thu, Sep 28, 2017 at 11:34 AM, Mark Engelberg 
>>> wrote:
>>>
 On Thu, Sep 28, 2017 at 11:02 AM, Jeaye  wrote:

> This has been the only issue we've run into with 1.9.0-beta1 ( ticket
> is here https://dev.clojure.org/jira/browse/CLJS-2352 ). On our
> back-end, all tests are good, but we can't currently use beta1 (or 
> alpha20)
> on the front-end, since this issue causes CLJS to choke. I'm hoping that a
> new version of CLJS comes out before Clojure 1.9.0 so that people don't 
> get
> the false impression that the latest of each is compatible with the other.
>
> J
>
>
 Agreed.  It is currently not possible to use Clojure 1.9.0 later than
 alpha19 with Clojurescript.  Clojurescript as it currently stands can't
 handle the new ## tags like ##Inf, ##NaN.  Like a number of people, I got
 burned by this when I tried to upgrade and spent some time tracking it
 down, only to realize it was already a known incompatibility.  There will
 be a lot more confused people if you release Clojure 1.9.0 prior to
 releasing a new version of Clojurescript that is compatible.

>>>
>>> --
>> 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 moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+unsubscr...@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+unsubscr...@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 clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help ship Clojure 1.9!

[Stuart Halloway]

Hi Aleš, Mark,

Thanks for the reports! It isn't clear to me how a change to tools.reader
can fix a problem with the core hash function. Can somebody point me to the
place in the Clojurescript code where this happens?

Stu

On Fri, Sep 29, 2017 at 11:13 AM, Aleš Roubíček  wrote:

> The Cljs problem is easily solvable by referencing latest tools.reader:
>
>  [org.clojure/clojurescript "1.9.908" :exclusions [org.clojure/tools.reader]]
>  [org.clojure/tools.reader "1.1.0"]
>
>
>
>
> On Thursday, September 28, 2017 at 8:37:11 PM UTC+2, puzzler wrote:
>>
>> And to be clear, it doesn't only affect people who try to use ##Inf or
>> ##NaN in their Clojurescript code.  It affects all existing Clojurescript
>> code, because running the Clojurescript compiler in a new version of
>> Clojure causes all Clojurescript code to emit these ## characters directly
>> into the javascript for its definition of the core hash function, which is
>> nonsensical javascript.  So all Clojurescript code is broken by running the
>> new release.
>>
>> On Thu, Sep 28, 2017 at 11:34 AM, Mark Engelberg 
>> wrote:
>>
>>> On Thu, Sep 28, 2017 at 11:02 AM, Jeaye  wrote:
>>>
 This has been the only issue we've run into with 1.9.0-beta1 ( ticket
 is here https://dev.clojure.org/jira/browse/CLJS-2352 ). On our
 back-end, all tests are good, but we can't currently use beta1 (or alpha20)
 on the front-end, since this issue causes CLJS to choke. I'm hoping that a
 new version of CLJS comes out before Clojure 1.9.0 so that people don't get
 the false impression that the latest of each is compatible with the other.

 J


>>> Agreed.  It is currently not possible to use Clojure 1.9.0 later than
>>> alpha19 with Clojurescript.  Clojurescript as it currently stands can't
>>> handle the new ## tags like ##Inf, ##NaN.  Like a number of people, I got
>>> burned by this when I tried to upgrade and spent some time tracking it
>>> down, only to realize it was already a known incompatibility.  There will
>>> be a lot more confused people if you release Clojure 1.9.0 prior to
>>> releasing a new version of Clojurescript that is compatible.
>>>
>>
>> --
> 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 moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@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+unsubscr...@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 clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help ship Clojure 1.9!

[Aleš Roubíček]

The Cljs problem is easily solvable by referencing latest tools.reader:

 [org.clojure/clojurescript "1.9.908" :exclusions [org.clojure/tools.reader]]
 [org.clojure/tools.reader "1.1.0"]




On Thursday, September 28, 2017 at 8:37:11 PM UTC+2, puzzler wrote:
>
> And to be clear, it doesn't only affect people who try to use ##Inf or 
> ##NaN in their Clojurescript code.  It affects all existing Clojurescript 
> code, because running the Clojurescript compiler in a new version of 
> Clojure causes all Clojurescript code to emit these ## characters directly 
> into the javascript for its definition of the core hash function, which is 
> nonsensical javascript.  So all Clojurescript code is broken by running the 
> new release.
>
> On Thu, Sep 28, 2017 at 11:34 AM, Mark Engelberg  > wrote:
>
>> On Thu, Sep 28, 2017 at 11:02 AM, Jeaye  
>> wrote:
>>
>>> This has been the only issue we've run into with 1.9.0-beta1 ( ticket is 
>>> here https://dev.clojure.org/jira/browse/CLJS-2352 ). On our back-end, 
>>> all tests are good, but we can't currently use beta1 (or alpha20) on the 
>>> front-end, since this issue causes CLJS to choke. I'm hoping that a new 
>>> version of CLJS comes out before Clojure 1.9.0 so that people don't get the 
>>> false impression that the latest of each is compatible with the other.
>>>
>>> J
>>>
>>>
>> Agreed.  It is currently not possible to use Clojure 1.9.0 later than 
>> alpha19 with Clojurescript.  Clojurescript as it currently stands can't 
>> handle the new ## tags like ##Inf, ##NaN.  Like a number of people, I got 
>> burned by this when I tried to upgrade and spent some time tracking it 
>> down, only to realize it was already a known incompatibility.  There will 
>> be a lot more confused people if you release Clojure 1.9.0 prior to 
>> releasing a new version of Clojurescript that is compatible. 
>>
>
>

-- 
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 moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help ship Clojure 1.9!

[Mark Engelberg]

And to be clear, it doesn't only affect people who try to use ##Inf or
##NaN in their Clojurescript code.  It affects all existing Clojurescript
code, because running the Clojurescript compiler in a new version of
Clojure causes all Clojurescript code to emit these ## characters directly
into the javascript for its definition of the core hash function, which is
nonsensical javascript.  So all Clojurescript code is broken by running the
new release.

On Thu, Sep 28, 2017 at 11:34 AM, Mark Engelberg 
wrote:

> On Thu, Sep 28, 2017 at 11:02 AM, Jeaye  wrote:
>
>> This has been the only issue we've run into with 1.9.0-beta1 ( ticket is
>> here https://dev.clojure.org/jira/browse/CLJS-2352 ). On our back-end,
>> all tests are good, but we can't currently use beta1 (or alpha20) on the
>> front-end, since this issue causes CLJS to choke. I'm hoping that a new
>> version of CLJS comes out before Clojure 1.9.0 so that people don't get the
>> false impression that the latest of each is compatible with the other.
>>
>> J
>>
>>
> Agreed.  It is currently not possible to use Clojure 1.9.0 later than
> alpha19 with Clojurescript.  Clojurescript as it currently stands can't
> handle the new ## tags like ##Inf, ##NaN.  Like a number of people, I got
> burned by this when I tried to upgrade and spent some time tracking it
> down, only to realize it was already a known incompatibility.  There will
> be a lot more confused people if you release Clojure 1.9.0 prior to
> releasing a new version of Clojurescript that is compatible.
>

-- 
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 moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help ship Clojure 1.9!

[Mark Engelberg]

On Thu, Sep 28, 2017 at 11:02 AM, Jeaye  wrote:

> This has been the only issue we've run into with 1.9.0-beta1 ( ticket is
> here https://dev.clojure.org/jira/browse/CLJS-2352 ). On our back-end,
> all tests are good, but we can't currently use beta1 (or alpha20) on the
> front-end, since this issue causes CLJS to choke. I'm hoping that a new
> version of CLJS comes out before Clojure 1.9.0 so that people don't get the
> false impression that the latest of each is compatible with the other.
>
> J
>
>
Agreed.  It is currently not possible to use Clojure 1.9.0 later than
alpha19 with Clojurescript.  Clojurescript as it currently stands can't
handle the new ## tags like ##Inf, ##NaN.  Like a number of people, I got
burned by this when I tried to upgrade and spent some time tracking it
down, only to realize it was already a known incompatibility.  There will
be a lot more confused people if you release Clojure 1.9.0 prior to
releasing a new version of Clojurescript that is compatible.

-- 
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 moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help ship Clojure 1.9!

[Ghadi Shayban]

Clojure 1.9 has been great for me so far. I think it's worth considering 
the problem Luke brought up regarding the REPL caught handler [1], 
especially since the compiler now checks macro specs. Having a slightly 
better knob for that might be nice, since it's an integration point.  (This 
is not an issue for socket REPL.) There are only 14 JIRAs tagged with 
rel1.9 that are not spec related [2].

[1] https://dev.clojure.org/jira/browse/CLJ-2040
[2] JIRA query: project = CLJ AND resolution = Unresolved AND fixVersion = 
"Release 1.9"  and labels != 'spec' ORDER BY priority DESC

On Thursday, September 28, 2017 at 10:00:16 AM UTC-4, stuart@gmail.com 
wrote:
>
> Clojure 1.9 has been quite stable throughout the alpha period, and we now 
> hope to release after a very short beta. Please test your existing programs 
> on the latest beta (see below), and respond on this thread ASAP if you 
> discover anything you believe to be a regression.
>
> Thanks!
> Stu
>
> ;; Clojure deps.edn
> org.clojure/clojure {:mvn/version "1.9.0-beta1"}
>
> ;; lein & boot
> [org.clojure/clojure "1.9.0-beta1"]
>
>

-- 
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 moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help ship Clojure 1.9!

[Jeaye]

This has been the only issue we've run into with 1.9.0-beta1 ( ticket is here 
https://dev.clojure.org/jira/browse/CLJS-2352 ). On our back-end, all tests are 
good, but we can't currently use beta1 (or alpha20) on the front-end, since 
this issue causes CLJS to choke. I'm hoping that a new version of CLJS comes 
out before Clojure 1.9.0 so that people don't get the false impression that the 
latest of each is compatible with the other.

J

On Thu, Sep 28, 2017 at 11:13:43AM -0400, Stuart Halloway wrote:
> Hi Nathan,
> 
> I suspect that is the same as
> https://github.com/clojure/clojurescript/commit/89914d2ead964122f99e638edda0cd96d330cb66.
> I don't have a sense of how many CLJS project this is going to cascade
> into, or what all will be needed. Anyone?
> 
> Stu
> 
> On Thu, Sep 28, 2017 at 10:44 AM, Nathan Fisher 
> wrote:
> 
> > Hi Stuart,
> >
> > Working to create a minimal test case but upgrading from alpha19 to beta1
> > seems to have broken lein-cljsbuild.
> >
> > I get the following error:
> >
> > >> snip >>
> >
> > *SEVERE:
> > /Users/nathanfisher/workspace/mklpq/target/cljsbuild-compiler-0/cljs/core.js:3579:
> > ERROR - Parse error. primary expression expected*
> >
> > *case ##Inf:*
> >
> > *  ^*
> >
> >
> > *Sep 28, 2017 3:23:10 PM com.google.javascript.jscomp.LoggerErrorManager
> > printSummary*
> >
> > *WARNING: 1 error(s), 0 warning(s)*
> >
> > *ERROR: JSC_PARSE_ERROR. Parse error. primary expression expected at
> > /Users/nathanfisher/workspace/mklpq/target/cljsbuild-compiler-0/cljs/core.js
> > line 3579 : 6*
> > << snip <<
> >
> > Changes in my project.clj deps are as follows:
> >
> > *- [org.clojure/clojure "1.9.0-alpha19" :scope "provided"]*
> >
> > *+ [org.clojure/clojure "1.9.0-beta1" :scope "provided"]*
> >
> > A revert on my project.clj to alpha19 eliminates the error.
> >
> > Cheers!
> >
> > Nathan
> >
> > On Thu, 28 Sep 2017 at 15:00 Stuart Halloway 
> > wrote:
> >
> >> Clojure 1.9 has been quite stable throughout the alpha period, and we now
> >> hope to release after a very short beta. Please test your existing programs
> >> on the latest beta (see below), and respond on this thread ASAP if you
> >> discover anything you believe to be a regression.
> >>
> >> Thanks!
> >> Stu
> >>
> >> ;; Clojure deps.edn
> >> org.clojure/clojure {:mvn/version "1.9.0-beta1"}
> >>
> >> ;; lein & boot
> >> [org.clojure/clojure "1.9.0-beta1"]
> >>
> >> --
> >> 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 moderated - please be patient with
> >> your first post.
> >> To unsubscribe from this group, send email to
> >> clojure+unsubscr...@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+unsubscr...@googlegroups.com.
> >> For more options, visit https://groups.google.com/d/optout.
> >>
> > --
> > - sent from my mobile
> >
> > --
> > 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 moderated - please be patient with
> > your first post.
> > To unsubscribe from this group, send email to
> > clojure+unsubscr...@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+unsubscr...@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 clojure@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+unsubscr...@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+unsubscr...@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 clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with 

Re: Help ship Clojure 1.9!

[Stuart Halloway]

Thanks Beau!

On Thu, Sep 28, 2017 at 1:06 PM, Beau Fabry  wrote:

> Identified an issue with prismatic/schema https://
> github.com/plumatic/schema/pull/399
>
> On Thursday, September 28, 2017 at 9:18:52 AM UTC-7, Nathan Fisher wrote:
>>
>> Hi Stuart,
>>
>> Looks like any project using lein-cljsbuild will be affected.
>>
>> I forked and bumped the Clojure and ClojureScript version to latest and
>> got the same error with their simple project:
>>
>> See Commit:
>> https://github.com/nfisher/lein-cljsbuild/commit/5df5d3c5bb4
>> 47b51a75abbbccdc72447814883a0
>>
>> STR
>>
>> 1. git clone https://github.com/nfisher/lein-cljsbuild
>> 2. cd lein-cljsbuild/example/projects/simple
>> 3. lein cljsbuild once
>>
>> Patch attached if you want to apply directly to
>> https://github.com/emezeske/lein-cljsbuild
>>
>> Cheers,
>> Nathan
>>
>> On Thu, 28 Sep 2017 at 16:13 Stuart Halloway 
>> wrote:
>>
>>> Hi Nathan,
>>>
>>> I suspect that is the same as https://github.com/clojure/clo
>>> jurescript/commit/89914d2ead964122f99e638edda0cd96d330cb66.  I don't
>>> have a sense of how many CLJS project this is going to cascade into, or
>>> what all will be needed. Anyone?
>>>
>>> Stu
>>>
>>> On Thu, Sep 28, 2017 at 10:44 AM, Nathan Fisher 
>>> wrote:
>>>
 Hi Stuart,

 Working to create a minimal test case but upgrading from alpha19 to
 beta1 seems to have broken lein-cljsbuild.

 I get the following error:

 >> snip >>

 *SEVERE:
 /Users/nathanfisher/workspace/mklpq/target/cljsbuild-compiler-0/cljs/core.js:3579:
 ERROR - Parse error. primary expression expected*

 *case ##Inf:*

 *  ^*


 *Sep 28, 2017 3:23:10 PM
 com.google.javascript.jscomp.LoggerErrorManager printSummary*

 *WARNING: 1 error(s), 0 warning(s)*

 *ERROR: JSC_PARSE_ERROR. Parse error. primary expression expected at
 /Users/nathanfisher/workspace/mklpq/target/cljsbuild-compiler-0/cljs/core.js
 line 3579 : 6*
 << snip <<

 Changes in my project.clj deps are as follows:

 *- [org.clojure/clojure "1.9.0-alpha19" :scope "provided"]*

 *+ [org.clojure/clojure "1.9.0-beta1" :scope "provided"]*

 A revert on my project.clj to alpha19 eliminates the error.

 Cheers!

 Nathan

 On Thu, 28 Sep 2017 at 15:00 Stuart Halloway 
 wrote:

> Clojure 1.9 has been quite stable throughout the alpha period, and we
> now hope to release after a very short beta. Please test your existing
> programs on the latest beta (see below), and respond on this thread ASAP 
> if
> you discover anything you believe to be a regression.
>
> Thanks!
> Stu
>
> ;; Clojure deps.edn
> org.clojure/clojure {:mvn/version "1.9.0-beta1"}
>
> ;; lein & boot
> [org.clojure/clojure "1.9.0-beta1"]
>
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clo...@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+u...@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+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
 --
 - sent from my mobile

 --
 You received this message because you are subscribed to the Google
 Groups "Clojure" group.
 To post to this group, send email to clo...@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+u...@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+u...@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 clo...@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+u...@googlegroups.com
>>> For more options, visit this group at
>>> 

Re: Help ship Clojure 1.9!

[Beau Fabry]

Identified an issue with 
prismatic/schema https://github.com/plumatic/schema/pull/399

On Thursday, September 28, 2017 at 9:18:52 AM UTC-7, Nathan Fisher wrote:
>
> Hi Stuart,
>
> Looks like any project using lein-cljsbuild will be affected.
>
> I forked and bumped the Clojure and ClojureScript version to latest and 
> got the same error with their simple project:
>
> See Commit:
>
> https://github.com/nfisher/lein-cljsbuild/commit/5df5d3c5bb447b51a75abbbccdc72447814883a0
>
> STR
>
> 1. git clone https://github.com/nfisher/lein-cljsbuild
> 2. cd lein-cljsbuild/example/projects/simple
> 3. lein cljsbuild once
>
> Patch attached if you want to apply directly to 
> https://github.com/emezeske/lein-cljsbuild
>
> Cheers,
> Nathan
>
> On Thu, 28 Sep 2017 at 16:13 Stuart Halloway  > wrote:
>
>> Hi Nathan,
>>
>> I suspect that is the same as 
>> https://github.com/clojure/clojurescript/commit/89914d2ead964122f99e638edda0cd96d330cb66.
>>   
>> I don't have a sense of how many CLJS project this is going to cascade 
>> into, or what all will be needed. Anyone?
>>
>> Stu
>>
>> On Thu, Sep 28, 2017 at 10:44 AM, Nathan Fisher > > wrote:
>>
>>> Hi Stuart,
>>>
>>> Working to create a minimal test case but upgrading from alpha19 to 
>>> beta1 seems to have broken lein-cljsbuild.
>>>
>>> I get the following error:
>>>
>>> >> snip >>
>>>
>>> *SEVERE: 
>>> /Users/nathanfisher/workspace/mklpq/target/cljsbuild-compiler-0/cljs/core.js:3579:
>>>  
>>> ERROR - Parse error. primary expression expected*
>>>
>>> *case ##Inf:*
>>>
>>> *  ^*
>>>
>>>
>>> *Sep 28, 2017 3:23:10 PM com.google.javascript.jscomp.LoggerErrorManager 
>>> printSummary*
>>>
>>> *WARNING: 1 error(s), 0 warning(s)*
>>>
>>> *ERROR: JSC_PARSE_ERROR. Parse error. primary expression expected at 
>>> /Users/nathanfisher/workspace/mklpq/target/cljsbuild-compiler-0/cljs/core.js
>>>  
>>> line 3579 : 6*
>>> << snip <<
>>>
>>> Changes in my project.clj deps are as follows: 
>>>
>>> *- [org.clojure/clojure "1.9.0-alpha19" :scope "provided"]*
>>>
>>> *+ [org.clojure/clojure "1.9.0-beta1" :scope "provided"]*
>>>
>>> A revert on my project.clj to alpha19 eliminates the error.
>>>
>>> Cheers!
>>>
>>> Nathan
>>>
>>> On Thu, 28 Sep 2017 at 15:00 Stuart Halloway >> > wrote:
>>>
 Clojure 1.9 has been quite stable throughout the alpha period, and we 
 now hope to release after a very short beta. Please test your existing 
 programs on the latest beta (see below), and respond on this thread ASAP 
 if 
 you discover anything you believe to be a regression.

 Thanks!
 Stu

 ;; Clojure deps.edn
 org.clojure/clojure {:mvn/version "1.9.0-beta1"}

 ;; lein & boot
 [org.clojure/clojure "1.9.0-beta1"]

 -- 
 You received this message because you are subscribed to the Google
 Groups "Clojure" group.
 To post to this group, send email to clo...@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+u...@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+u...@googlegroups.com .
 For more options, visit https://groups.google.com/d/optout.

>>> -- 
>>> - sent from my mobile
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google
>>> Groups "Clojure" group.
>>> To post to this group, send email to clo...@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+u...@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+u...@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 clo...@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+u...@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 

Re: Help ship Clojure 1.9!

[Nathan Fisher]

Hi Stuart,

Looks like any project using lein-cljsbuild will be affected.

I forked and bumped the Clojure and ClojureScript version to latest and got
the same error with their simple project:

See Commit:
https://github.com/nfisher/lein-cljsbuild/commit/5df5d3c5bb447b51a75abbbccdc72447814883a0

STR

1. git clone https://github.com/nfisher/lein-cljsbuild
2. cd lein-cljsbuild/example/projects/simple
3. lein cljsbuild once

Patch attached if you want to apply directly to
https://github.com/emezeske/lein-cljsbuild

Cheers,
Nathan

On Thu, 28 Sep 2017 at 16:13 Stuart Halloway 
wrote:

> Hi Nathan,
>
> I suspect that is the same as
> https://github.com/clojure/clojurescript/commit/89914d2ead964122f99e638edda0cd96d330cb66.
> I don't have a sense of how many CLJS project this is going to cascade
> into, or what all will be needed. Anyone?
>
> Stu
>
> On Thu, Sep 28, 2017 at 10:44 AM, Nathan Fisher 
> wrote:
>
>> Hi Stuart,
>>
>> Working to create a minimal test case but upgrading from alpha19 to beta1
>> seems to have broken lein-cljsbuild.
>>
>> I get the following error:
>>
>> >> snip >>
>>
>> *SEVERE:
>> /Users/nathanfisher/workspace/mklpq/target/cljsbuild-compiler-0/cljs/core.js:3579:
>> ERROR - Parse error. primary expression expected*
>>
>> *case ##Inf:*
>>
>> *  ^*
>>
>>
>> *Sep 28, 2017 3:23:10 PM com.google.javascript.jscomp.LoggerErrorManager
>> printSummary*
>>
>> *WARNING: 1 error(s), 0 warning(s)*
>>
>> *ERROR: JSC_PARSE_ERROR. Parse error. primary expression expected at
>> /Users/nathanfisher/workspace/mklpq/target/cljsbuild-compiler-0/cljs/core.js
>> line 3579 : 6*
>> << snip <<
>>
>> Changes in my project.clj deps are as follows:
>>
>> *- [org.clojure/clojure "1.9.0-alpha19" :scope "provided"]*
>>
>> *+ [org.clojure/clojure "1.9.0-beta1" :scope "provided"]*
>>
>> A revert on my project.clj to alpha19 eliminates the error.
>>
>> Cheers!
>>
>> Nathan
>>
>> On Thu, 28 Sep 2017 at 15:00 Stuart Halloway 
>> wrote:
>>
>>> Clojure 1.9 has been quite stable throughout the alpha period, and we
>>> now hope to release after a very short beta. Please test your existing
>>> programs on the latest beta (see below), and respond on this thread ASAP if
>>> you discover anything you believe to be a regression.
>>>
>>> Thanks!
>>> Stu
>>>
>>> ;; Clojure deps.edn
>>> org.clojure/clojure {:mvn/version "1.9.0-beta1"}
>>>
>>> ;; lein & boot
>>> [org.clojure/clojure "1.9.0-beta1"]
>>>
>>> --
>>> 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 moderated - please be patient with
>>> your first post.
>>> To unsubscribe from this group, send email to
>>> clojure+unsubscr...@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+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> - sent from my mobile
>>
>> --
>> 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 moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+unsubscr...@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+unsubscr...@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 clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
-- 
- sent from my mobile

-- 
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: Help ship Clojure 1.9!

[Stuart Halloway]

Hi Nathan,

I suspect that is the same as
https://github.com/clojure/clojurescript/commit/89914d2ead964122f99e638edda0cd96d330cb66.
I don't have a sense of how many CLJS project this is going to cascade
into, or what all will be needed. Anyone?

Stu

On Thu, Sep 28, 2017 at 10:44 AM, Nathan Fisher 
wrote:

> Hi Stuart,
>
> Working to create a minimal test case but upgrading from alpha19 to beta1
> seems to have broken lein-cljsbuild.
>
> I get the following error:
>
> >> snip >>
>
> *SEVERE:
> /Users/nathanfisher/workspace/mklpq/target/cljsbuild-compiler-0/cljs/core.js:3579:
> ERROR - Parse error. primary expression expected*
>
> *case ##Inf:*
>
> *  ^*
>
>
> *Sep 28, 2017 3:23:10 PM com.google.javascript.jscomp.LoggerErrorManager
> printSummary*
>
> *WARNING: 1 error(s), 0 warning(s)*
>
> *ERROR: JSC_PARSE_ERROR. Parse error. primary expression expected at
> /Users/nathanfisher/workspace/mklpq/target/cljsbuild-compiler-0/cljs/core.js
> line 3579 : 6*
> << snip <<
>
> Changes in my project.clj deps are as follows:
>
> *- [org.clojure/clojure "1.9.0-alpha19" :scope "provided"]*
>
> *+ [org.clojure/clojure "1.9.0-beta1" :scope "provided"]*
>
> A revert on my project.clj to alpha19 eliminates the error.
>
> Cheers!
>
> Nathan
>
> On Thu, 28 Sep 2017 at 15:00 Stuart Halloway 
> wrote:
>
>> Clojure 1.9 has been quite stable throughout the alpha period, and we now
>> hope to release after a very short beta. Please test your existing programs
>> on the latest beta (see below), and respond on this thread ASAP if you
>> discover anything you believe to be a regression.
>>
>> Thanks!
>> Stu
>>
>> ;; Clojure deps.edn
>> org.clojure/clojure {:mvn/version "1.9.0-beta1"}
>>
>> ;; lein & boot
>> [org.clojure/clojure "1.9.0-beta1"]
>>
>> --
>> 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 moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+unsubscr...@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+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> - sent from my mobile
>
> --
> 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 moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@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+unsubscr...@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 clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help ship Clojure 1.9!

[Nathan Fisher]

Hi Stuart,

Working to create a minimal test case but upgrading from alpha19 to beta1
seems to have broken lein-cljsbuild.

I get the following error:

>> snip >>

*SEVERE:
/Users/nathanfisher/workspace/mklpq/target/cljsbuild-compiler-0/cljs/core.js:3579:
ERROR - Parse error. primary expression expected*

*case ##Inf:*

*  ^*


*Sep 28, 2017 3:23:10 PM com.google.javascript.jscomp.LoggerErrorManager
printSummary*

*WARNING: 1 error(s), 0 warning(s)*

*ERROR: JSC_PARSE_ERROR. Parse error. primary expression expected at
/Users/nathanfisher/workspace/mklpq/target/cljsbuild-compiler-0/cljs/core.js
line 3579 : 6*
<< snip <<

Changes in my project.clj deps are as follows:

*- [org.clojure/clojure "1.9.0-alpha19" :scope "provided"]*

*+ [org.clojure/clojure "1.9.0-beta1" :scope "provided"]*

A revert on my project.clj to alpha19 eliminates the error.

Cheers!

Nathan

On Thu, 28 Sep 2017 at 15:00 Stuart Halloway 
wrote:

> Clojure 1.9 has been quite stable throughout the alpha period, and we now
> hope to release after a very short beta. Please test your existing programs
> on the latest beta (see below), and respond on this thread ASAP if you
> discover anything you believe to be a regression.
>
> Thanks!
> Stu
>
> ;; Clojure deps.edn
> org.clojure/clojure {:mvn/version "1.9.0-beta1"}
>
> ;; lein & boot
> [org.clojure/clojure "1.9.0-beta1"]
>
> --
> 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 moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
-- 
- sent from my mobile

-- 
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 moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Help ship Clojure 1.9!

[Stuart Halloway]

Clojure 1.9 has been quite stable throughout the alpha period, and we now
hope to release after a very short beta. Please test your existing programs
on the latest beta (see below), and respond on this thread ASAP if you
discover anything you believe to be a regression.

Thanks!
Stu

;; Clojure deps.edn
org.clojure/clojure {:mvn/version "1.9.0-beta1"}

;; lein & boot
[org.clojure/clojure "1.9.0-beta1"]

-- 
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 moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.