Re: (Request) Rich Hickey's EuroClojure 2014 slides

Usually Rich doesn't release his slides as he prefers for them to be consumed in the context of the talk. On Thursday, September 11, 2014 8:44:47 AM UTC-5, Leon Grapenthin wrote: > > Hi, > I am looking for the slides of this talk because one can't see them in > the video: > > http://vimeo.com/1

Re: Pause a go loop

You should never block a go loop other than by using a parking channel op (like !, etc). You probably instead want a control channel where you can send it a pause message telling it to block on the control channel until a resume message arrives. On Thursday, September 11, 2014 6:52:48 AM UTC-5

Re: defrecord - CompilerException to referring record defined at other namespace

>Record2 > > On Wednesday, September 10, 2014 10:21:45 PM UTC+8, Alex Miller wrote: >> >> Is datatypes.clj at src/defrecord_example1/datatypes.clj ? (note _, not >> - in directory name) >> >> >> On Wednesday, September 10, 2014 6:01:25 AM UTC-5, Bin Li

Re: [ANN] Clojure 1.7.0-alpha2

On Thursday, September 11, 2014 2:41:44 AM UTC-5, Arnout Roemers wrote: > > I can understand why something like a clojure.lang.Volatile can be useful > for some optimizations in the functions of standard library, but do they > really need to become part of the public core API? > >From my own pe

Re: (Request) Rich Hickey's EuroClojure 2014 slides

hin > wrote: > >> @Alex Miller: It would be great if an exception could be made. Again: The >> slides are not in the video. >> >> Consuming them "in context of the talk" is my intention by opening two >> windows (one with the video, one with the slides).

Re: Clojure terminology

On Thursday, September 11, 2014 2:49:43 PM UTC-5, jvanderhyde wrote: > > I'm new to Clojure, but I'm teaching a course on it this year to > undergrads. I'm having a little trouble with terminology, partly because > Clojure departs from other languages (such as Scheme) on some terms (such > as

Re: convert between PersistentArrayMap and HashMap

Well first I'd say that the Java api you're calling into isn't very good if it expects specifically java.util.HashMap. Clojure's map data structures implement java.util.Map so generally they can be passed into Java api methods that take the interface (good practice). However, HashMap has a cons

Rich Hickey's Transducers talk from Strange Loop

For your enjoyment... https://www.youtube.com/watch?v=6mTbuzafcII -- 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 yo

clojure.org uses a wikispaces TLS certificate

Clojure.org is hosted on wikispaces. For what purpose would you access it by https? -- 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

Re: clojure.org uses a wikispaces TLS certificate

aurens Van Houtven wrote: > > Hi Alex, > > On 20 Sep 2014, at 20:20, Alex Miller > > wrote: > > > Clojure.org is hosted on wikispaces. For what purpose would you access > it by https? > > It’s not a (purposeful) choice; my browser is configured to access any

Re: Eager (cat) in transducers

This is an excellent question and the answer is: no, there is not a clever way (or a desire) to avoid this. The internals of transducer functions are never lazy. Each "step" will be eagerly completed for each output element. This is a fundamental difference between the lazy sequence and transdu

ANN: State of Clojure 2014 Survey - please contribute!!

ommunity perspective, it is really great to see this feedback every year to gauge the size and interests of the community. Both raw data and some analysis will be published after the survey ends on October 17th. Let me know if you have any questions, Alex Miller alex.mil...@cognitect.com -- You recei

Re: uniqueness of hash if computed on different jvms across different machines.

I would expect that right now the same version of Clojure would typically give you the same hash for the same data structure across different JVM instances. HOWEVER, I would consider this accidental, not a guarantee. Certainly the hash values may change across Clojure or JDK versions. Additiona

Re: Keyword comparison performance

Not really chiming in directly on this, but one thing I wanted to note is that getting meaningful performance numbers for keyword-related code is somewhat tricky due to caching and interning. Keywords are cached so new keyword construction is much slower than existing keyword construction (and

Re: ANN: State of Clojure 2014 Survey - please contribute!!

I'd be happy to include these for consideration next year. I think on the dev env we have removed some like this because they were not well represented in the results. The landscape for dev envs changes significantly year to year. On Wednesday, October 8, 2014 11:32:53 PM UTC-5, Mars0i wrote: >

Re: ANN: State of Clojure 2014 Survey - please contribute!!

Hey Zack, I don't know that we will include demographic questions in this survey in the future, something to think about. I do not need a poll to see that Clojure developers are predominantly white men, although that's also true of most programming languages and a consequence of larger pervas

2014 State of Clojure & ClojureScript Survey ends Oct 17th

Just a reminder that this Friday is the last day to complete the 2014 State of Clojure & ClojureScript surveys: http://blog.cognitect.com/blog/2014/10/3/2014-state-of-clojure-clojurescript-survey So far 1110 people have filled out the State of Clojure survey and 544 people have filled out the Sta

Re: book for a beginner with some exercises

There are a number of sites with Clojure exercises (Clojure Koans, 4 Clojure, Exercism.io). Of those, I like 4 Clojure the most for what you're describing. Marick's "Functional Programming for the Object-Oriented Programmer" https://leanpub.com/fp-oo has really great exercises in it. Parts of

Re: [ClojureScript] 2014 State of Clojure & ClojureScript Survey ends Oct 17th

nt. No hard deadline though. > > On Sunday, 19 October 2014, Yehonathan Sharvit wrote: > On Tuesday, 14 October 2014 16:21:13 UTC+3, Alex Miller  wrote: > > > Just a reminder that this Friday is the last day to complete the 2014 State > > of Clojure & ClojureScript

State of Clojure/ClojureScript 2014 survey results

I've published links to the State of Clojure and ClojureScript 2014 survey results here: http://blog.cognitect.com/blog/2014/10/20/results-of-2014-state-of-clojure-and-clojurescript-survey That page links to some reports with graphs where you can also export the raw data. I also have links to brok

Re: State of Clojure/ClojureScript 2014 survey results

ww.youtube.com/watch?v=3MvKLOecT1I which does a great analysis > job on a similar survey for Erlang. > > On Thu, Oct 23, 2014 at 4:58 PM, Alex Miller > wrote: > >> I've published links to the State of Clojure and ClojureScript 2014 >> survey results here: &

Re: Demoralising experience trying to install on Win 7

Hey Geoff, I just wanted to say that I really appreciate you bringing a detailed walkthrough of your experience and the pain points here. It certainly highlights some obstacles and things that can be better. I will be discussing this more with other people at Cognitect and I would like to make

[ANN] Clojure 1.7.0-alpha3 now available

Clojure 1.7.0-alpha3 is now available. Try it via - Download: http://central.maven.org/maven2/org/clojure/clojure/1.7.0-alpha3/ - Download securely: https://repo1.maven.org/maven2/org/clojure/clojure/1.7.0-alpha3/ - Leiningen: [org.clojure/clojure "1.7.0-alpha3"] For users of Clojure 1.7.0-alpha2

Re: [ANN] Clojure 1.7.0-alpha3 now available

treme circumstances. I was thinking of macro'ing it out to > an arity of 20, but > haven't yet, just because it seems a step too far. > > Phil > > > > From: clo...@googlegroups.com [clo...@googlegroups.com > ] on beha

Re: [ANN] Clojure 1.7.0-alpha3 now available

On Monday, October 27, 2014 9:36:02 AM UTC-5, Phillip Lord wrote: > > > And the performance boost is just to avoid the list creation in the > variadic argument? > Yes. There's some perf timings in the ticket. -- You received this message because you are subscribed to the Google Groups "Clojure

Re: CCW bug [SEVERE]

On Monday, October 27, 2014 10:21:35 AM UTC-5, Fluid Dynamics wrote: > > >> > I'm not going through the ritual of check-in and check-back-out every > single time I'd normally hit control-S. Too much friction, too much > work-that-isn't-development. > Doesn't Eclipse already have a local file

Re: [ANN] Clojure 1.7.0-alpha3 now available

We will definitely be rolling this particular aspect of CLJ-1330 back in the next release. Alex On Tuesday, October 28, 2014 10:44:51 AM UTC-5, Sam Ritchie wrote: > > Yeah, I'm getting this too with a file named "wparankings.clj". I haven't > investigated which function is causing this, but thi

Re: [ANN] Clojure 1.7.0-alpha3 now available

ete at first glance. > > > On Tuesday, October 28, 2014 9:53:05 PM UTC+1, Alex Miller wrote: >> >> We will definitely be rolling this particular aspect of CLJ-1330 back in >> the next release. >> >> Alex >> >> On Tuesday, October 28, 2014 10:44:51

Re: How is Matthias' transcripts license going?

iver the contents to Japanese Clojure community. But before > that, I want to clear how their license is going. In his repository, > Matthias is saying he has no authority to grant a license of them. Also, on > the other hand, I saw Alex Miller (one of their right holders) allowed h

Re: CCW bug [SEVERE]

This thread needs to end, it's no longer productive. Fluid Dynamics - file a ticket for CCW with information useful for addressing the problem if you have it. Otherwise, I do not think there is anything left that anyone can help you with here. Everyone else - thank your for all the helpful co

Re: On Testing

It would be great if someone could enumerate more explicitly what "better" test output means. What are the specific problems in the current test output reporting? Similar problem list for test runner might be useful. Discussion here is fine but ultimately needs to land on a design wiki page. I

Re: On Testing

Additionally, I think it would be helpful to enumerate example (failing) tests and their output by current clojure.test. On Saturday, November 1, 2014 1:58:32 PM UTC-5, Alex Miller wrote: > > It would be great if someone could enumerate more explicitly what "better" > test

Re: Clojure usage in production - survey on Hacker News (Nov 2014)

I was mostly trying to include interesting companies using it for something. Sorry if I overstepped! :) On Monday, November 3, 2014 6:27:41 PM UTC-6, viksit wrote: > > > Ashton - perhaps you should elucidate on matters on that thread :) And why > do you say "stretching" definitions? > > > On Mon

Re: About transients no longer being safe in 1.7-alpha2

On Monday, November 3, 2014 9:00:10 PM UTC-6, Atamert Ölçgen wrote: > > > > On Mon, Nov 3, 2014 at 5:57 PM, Daniel Marjenburgh > wrote: > >> Hi, >> >> I just want to address this issue (CLJ-1498 >> ). It was accepted in >> 1.7-alpha2 and I haven't s

Re: About transients no longer being safe in 1.7-alpha2

ients are values (not reference types like ref or atom) I > can't think of a case where they can be modified concurrently. > You can, but not without going pretty far out of normal Clojure code. > > > On Tue, Nov 4, 2014 at 11:19 AM, Alex Miller > wrote: > >&

Re: About transients no longer being safe in 1.7-alpha2

I think all of these examples violate the usage expectations of transients (regardless of release) and you should expect to get confusing results from them. I do not think it's worth modifying core.async go blocks to do anything special in this regard (eince go is a macro I don't think you can

Re: Clojure usage in production - survey on Hacker News (Nov 2014)

I've added the list of companies using Clojure to clojure.org at http://clojure.org/Companies - feel free to ping me at alex.mil...@cognitect.com or here if you want something added/removed/changed. Alex -- You received this message because you are subscribed to the Google Groups "Clojure" gr

Re: Clojure CLR Experiences

On Tuesday, November 11, 2014 9:38:58 AM UTC-6, Adrian Mowat wrote: > > > * Is it sensible to think in terms of writing platform independent code in > the same way as we do with cljx files in ClojureScript? > With the feature expressions work we hope to include in 1.7, this will become possibl

[ANN] Clojure 1.7.0-alpha4 now available

Clojure 1.7.0-alpha4 is now available. Try it via - Download: http://central.maven.org/maven2/org/clojure/clojure/1.7.0-alpha4/ - Download securely: https://repo1.maven.org/maven2/org/clojure/clojure/1.7.0-alpha4/ - Leiningen: [org.clojure/clojure "1.7.0-alpha4"] A few important changes to be awa

Re: [ANN] Clojure 1.7.0-alpha4 now available

! Alex On Friday, November 14, 2014 1:34:55 PM UTC-6, Alex Miller wrote: > > Clojure 1.7.0-alpha4 is now available. > > Try it via > - Download: > http://central.maven.org/maven2/org/clojure/clojure/1.7.0-alpha4/ > - Download securely: > https://repo1.maven.org/maven2/o

Re: Weird performance issue with reduce

What version of Clojure are you using? This seems like a use case where transducers could help significantly in avoiding lazy effects and intermediate objects. On Monday, November 17, 2014 4:28:12 AM UTC-6, Alexander L. wrote: > > Hi all, > > I understand that the following question is a long s

Re: 1.6.X latest branch

On Monday, December 8, 2014 9:01:06 PM UTC-6, Andy Fingerhut wrote: > > I can't state authoritatively why, but here is some evidence: > > 1.1.x and 1.3.x are identical to 1.1.0 and 1.3.0. > > 1.2.x and 1.5.x are equivalent to 1.2.1 and 1.5.1, respectively, which do > have a few bug fixes made af

Re: Status of lean runtime?

We are still very interested in improving both Clojure load times and pursuing multiple build profiles. That work will not be part of 1.7. Alex -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups

Re: Status of lean runtime?

I've done a fair amount of testing on fastload for Rich, as well as on the direct branch, which further extends some experimental work on static var invocation. Fastload does indeed reduce startup time by making var loading lazy. However, it also adds an additional check into the var invocation

Re: Status of lean runtime?

I also meant to mention that I built working version of the build profile stuff and got about halfway through an overhaul of the build system as well this past summer but it's never been in a form that was complete enough to make public anywhere. I expect that to re-surface as well. -- You rec

Re: Status of lean runtime?

Ditto what Sean said. There's no decision yet but I plan to recommend dropping Java 1.6 in Clojure 1.8. I expect we'll gather more input on it before it happens though. Alex On Thursday, December 11, 2014 2:11:28 PM UTC-6, Sean Corfield wrote: > > Java 6 has been EOL for nearly two years. Java

Has the old "invalid constant tag: -57" bug been fixed?

If you could refer to a ticket, an example, or really any other information, that might be a question I could answer. It doesn't ring a bell. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.co

Re: Codox output missing namespace documentation

If it is AOT, then you're probably seeing this issue: http://dev.clojure.org/jira/browse/CLJ-130 On Tuesday, December 16, 2014 11:02:22 AM UTC-6, Nick Gonzalez wrote: > I'm using codox to generate api documentation for a fairly large Cojure > project, and it is ignoring namespace doc strings for

Re: Clojure and IBM JVM

The problem is in the static initializer (which is gigantic), not the particular 2-liner, which is being called when the class loads. Here's the disassembled bytecode: https://gist.github.com/puredanger/40dd3ec22fdb5836d1eb On a first pass through it's not obvious to me what's causing the bloat

Re: Questions about Clojure 1.7 Release / Process / Helping Out

Hi David! On Tuesday, December 30, 2014 4:01:27 PM UTC-6, David James wrote: > > My questions are: (Please let me know if I've overlooked links to read.) > >- Does Rich or Clojure Core have rough dates in mind for the 1.7 >release? Any idea? (I wouldn't be surprised at all if dates were n

Re: core async and transducers in Clojure 1.6.0

inc all the other responses in this thread but will also point at this example in the core.async tests that defines a transducer (works in 1.6) as an example: https://github.com/clojure/core.async/blob/master/src/test/clojure/clojure/core/pipeline_test.clj#L6 On Monday, December 29, 2014 10:38

[ANN] Clojure 1.7.0-alpha5 now available

Clojure 1.7.0-alpha5 is now available. Try it via - Download: https://repo1.maven.org/maven2/org/clojure/clojure/1.7.0-alpha5/ - Leiningen: [org.clojure/clojure "1.7.0-alpha5"] A few of the highlights in alpha5: 1) New transducer arities for map-indexed, distinct, and interpose. The transducer v

[ANN] Clojure 1.7.0-alpha5 now available

I would greatly appreciate hearing any feedback about this (or any other) alpha, even if it's just: everything looks ok. We've had a couple of regressions reported and that is hugely helpful as we can quickly turn around fixes for the next one. Interested particularly in: regressions, perfor

Re: [ANN] Clojure 1.7.0-alpha5 now available

No, we do not work from planned release dates. When it's done, we ship it. The current plan is to do at least one more alpha with a version of feature expressions that is a bit slimmer than the current available patches to make that available for people to experiment (presumably along with tool

Re: [ANN] Clojure 1.7.0-alpha5 now available

Thanks Sean. I'm hoping to get new releases of core.cache and core.menoize in th near future too but seems worth looking into. -- 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 pos

Re: [ANN] Clojure 1.7.0-alpha5 now available

can see. > > Thanks, > Rangel > @raspasov > > On Sunday, January 11, 2015 at 6:34:07 AM UTC-8, Alex Miller wrote: >> >> I would greatly appreciate hearing any feedback about this (or any other) >> alpha, even if it's just: everything looks ok. >>

Re: [ANN] Clojure 1.7.0-alpha5 now available

nvoke(RestFn.java:425) > > at clojure.tools.analyzer.jvm$analyze.invoke(jvm.clj:474) > > at clojure.tools.analyzer.jvm$analyze.invoke(jvm.clj:467) > > at > clojure.core.async.impl.ioc_macros$state_machine.invoke(ioc_macros.clj:1062) > > >

Re: [ANN] Clojure 1.7.0-alpha5 now available

g.PersistentVector.create(Ljava/util/List;)Lclojure/lang/PersistentVector; >> >> >> I can fix the library, I don't think it will be a big problem, just >> making sure that's something you guys were OK with breaking - it's more >> like an implementation d

Re: [ANN] Clojure 1.7.0-alpha5 now available

I would be helpful to me at this point to have a jira regarding this problem which I will presume for the time being is the same in both Andy and Sean's case. On Monday, January 12, 2015 at 11:30:57 AM UTC-6, Andy Fingerhut wrote: > > Nicola, Sean: > > I am _not_ testing with Sean's code, so can

Re: core.async buffers alternative backend

I don't actually remember now, but it's possible that when core.async was created we were still trying to accommodate an older version of Java before some of those existed. That's not an issue now as we only need to support Java 1.8+. So, I don't know of any reason these wouldn't be an option.

Re: Classpath bug re Clojure 1.10.1.645 when using Figwheel.Main

s the changes in the release that led to the issue here. Additionally, libs are now sorted by tree depth (roots first, then their deps, etc), then alpha per depth so this should greatly improve reproducibility of lib ordering across builds. On Monday, September 14, 2020 at 7:51:07 AM UTC-5 Alex M

Clojure 1.10.2-rc1

Clojure 1.10.2-rc1 is now available. This is a release candidate and we would appreciate it if you could try it in your own projects. If you encounter issues, https://ask.clojure.org is the best place to file a report. Below is a changelog for 1.10.2 (items new to this release since 1.10.2-alph

Cognitect and Nubank are Sponsoring Open Source Developers

https://cognitect.com/blog/2020/12/15/sponsoring-open-source-developers -- 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 wi

Re: Unexpected "#_ - Discard" error

The discard reader will read, then discard (so the following form still has to be readable). In this case, the 1:2 starts with a number so is parsed as one, but that's an invalid form. On Saturday, April 3, 2021 at 8:50:49 AM UTC-5 zen...@gmail.com wrote: > I'm reading https://clojure.org/guid

Re: Reporting Potential Security Vulnerabilities in the Clojure Codebase

If you want to report something privately, you can email it to cloj...@cognitect.com. Alex On Saturday, July 17, 2021 at 2:21:56 PM UTC-5 William Blair wrote: > > Does the Clojure project have a protocol in place for reporting potential > security vulnerabilities found in the runtime? I'd be

Re: ClassNotFoundException when importing a clojure interface

definterface is generally considered a low-level tool in Clojure and typically Clojure developers do not create interfaces directly like this. The two primary means of function abstraction/polymorphism are multimethods (can dispatch on any aspect of any of the parameters to a function) and prot

Re: how to package a project to a jar file?

You might want to check out the tools.build project. https://clojure.org/guides/tools_build On Tuesday, September 14, 2021 at 10:35:24 AM UTC-5 yccal...@gmail.com wrote: > i can't use lein > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post

Clojure 1.11 is now available!

You can find an overview here: https://clojure.org/news/2022/03/22/clojure-1-11-0 And full changelog here: https://github.com/clojure/clojure/blob/master/changes.md#changes-to-clojure-in-version-1110 Enjoy! -- You received this message because you are subscribed to the Google Groups "Clojure" g

Re: Book project : compilation of Rich Hickey conferences transcripts translated in french

Hi Paul, contact me at alex.mil...@cognitect.com. I will say that if anyone wants to do translations / transcriptions in other languages for anything on ClojureTV, I am more than happy to add those to the video. Alex On Tuesday, May 24, 2022 at 6:21:02 AM UTC-5 paul@gmail.com wrote: > Hi,

Re: Any updates on spec after “Maybe Not” presentation?

The schema and select support has been added to spec in spec2 (https://github.com/clojure/spec-alpha2) but is still a work in progress. You can find more info at https://github.com/clojure/spec-alpha2/wiki/Schema-and-select . Alex On Thursday, May 19, 2022 at 4:12:33 PM UTC-5 Dmitry Kakurin wr

State of Clojure 2023 Survey

Hello, the annual State of Clojure 2023 survey is now open! This survey has been done every year since 2010 and has been instrumental in tracking changes in the Clojure community over time. https://www.surveymonkey.com/r/clojure2023 We would greatly appreciate it if you could complete this by

Re: [ANN] Clojure 1.9.0-alpha1

On Tuesday, May 24, 2016 at 5:45:47 PM UTC-5, Sean Corfield wrote: > > We have 1.9.0 Alpha 1 in QA at World Singles and plan to start using > clojure.spec this week. We’ve gone to production on Alpha builds ever since > 1.3 and almost never had any problems (in five years – time has flown > pas

Re: [ANN] Clojure 1.9.0-alpha1

On Tuesday, May 24, 2016 at 7:26:57 PM UTC-5, Leif wrote: > > Hi, Alex, thanks for the responsiveness. > > The paths refer to tags in the schemas, not keys in the map. However, this >> has been asked about several times today and Rich has added support for a >> :in clause that will track the ke

Re: [ANN] Clojure 1.9.0-alpha1

Probably - can you file a jira for that? On Tuesday, May 24, 2016 at 10:53:43 PM UTC-5, Ambrose Bonnaire-Sergeant wrote: > > Thanks for the guide Alex. > > Is it possible to get more information in the "no method" error returned by > multi-spec? > > (s/explain :event/event {:event/type :event/res

Re: [ANN] Clojure 1.9.0-alpha1

So something like (defn valid-or-explain [spec data] (let [v (s/valid? spec data)] (when-not v (s/explain spec data)) v)) I'll mention it to Rich, not sure though. On Tuesday, May 24, 2016 at 10:56:03 PM UTC-5, puzzler wrote: > > One thing that has always limited the value of pre and

Re: [ANN] Clojure 1.9.0-alpha1

We will be adding CLJ-1910 and CLJ-1919 for namespaced map literals and namespaced map destructuring in an alpha relatively soon. Nothing else to announce re 1.9 right now. On Wednesday, May 25, 2016 at 1:52:33 AM UTC-5, Tatu Tarvainen wrote: > > > Are there plans for what will be the release c

Re: [ANN] Clojure 1.9.0-alpha1

We do not plan to create or support a backport lib for Clojure 1.8. Mostly just a matter of choosing not to spend our time on maintaining multiple code bases. On Wednesday, May 25, 2016 at 8:34:41 AM UTC-5, Gary Trakhman wrote: > > It would be helpful to make clojure.spec available as a lib for

Re: clojure.spec

You can get the registry with (s/registry), which is just a map of spec names (namespaced keywords) to the spec. Is that what you're looking for? If you have registered (s/def ::foo string?) then you can find the spec with (::foo (s/registry)) On Wednesday, May 25, 2016 at 7:37:07 AM UTC-5, Gar

Re: clojure.spec

As mentioned in the guide, while conformers can be used to implement coercions, that is something you should think about very carefully. When you register a spec with a conformer, you are making a choice for all possible future consumers of that spec as to how they are getting the conformed dat

Re: [ANN] Clojure 1.9.0-alpha1

Rich pointed out that this is telling you the predicate :my.domain/event-type and the value it received: {:event/type :event/restart} which seems to be telling you everything you need to know wrt to the missing method. The dispatch method is opaque (even though it is simple here), so doesn't

Re: clojure.spec

Hopefully this will be made more clear in another guide about generators and testing. As soon as we have time to write it. :) On Wednesday, May 25, 2016 at 10:12:54 AM UTC-5, kovasb wrote: > > > This seems like an important point, that didn't really come through (for > me at least) in the docs s

Re: clojure.spec

Coming. On Wednesday, May 25, 2016 at 10:59:52 AM UTC-5, JvJ wrote: > > Any plans for cljs support? > -- 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 m

[ANN] Clojure 1.9.0-alpha2

lojure 1.9.0-alpha2 is now available. Try it via - Download: https://repo1.maven.org/maven2/org/clojure/clojure/1.9.0-alpha2 - Leiningen: [org.clojure/clojure "1.9.0-alpha2"] 1.9.0-alpha2 includes the following changes since 1.9.0-alpha1: - Better describe for s/+ - Capture *recursion-limit* on

Re: clojure.spec

I do actually have specs for spec and it would catch these. :) You can try it yourself though: (s/def ::s/req (s/* keyword?)) (s/def ::s/req-un (s/* keyword?)) (s/def ::s/opt (s/* keyword?)) (s/def ::s/opt-un (s/* keyword?)) (s/fdef s/keys :args (s/cat :form ::s/any :env ::s/any;; form/en

Re: clojure.spec

s/or creates a spec and s/alt creates a regex op. Regex ops can be combined to describe a single sequence. Use s/alt if you are matching alternative regex expressions in a sequential context - in particular where the branches of the alt are themselves regex ops. Use s/or when matching a single

Re: clojure.spec

I forgot to mention that if you run this with alpha2, this example won't work due to a bug, but that is fixed in master for alpha3. On Wednesday, May 25, 2016 at 2:38:07 PM UTC-5, Alex Miller wrote: > > s/or creates a spec and s/alt creates a regex op. Regex ops can be > combined

Re: clojure spec fdef

It's a little tricky but you want: (s/fdef remove-autoinc-columns :args (s/cat :cols (s/spec ::columns))) Here the args data is ([{:foo "some_t"}]) and while you have an s/cat for :args and an s/cat in ::columns, those will be combined into the same regex so that's basically the same thing as :

Re: clojure spec fdef

n my fist bummer. > > Do you have an example for this in the guide? I did not fully read it, but > I think I scrolled through everything that used fdefs. > > Best Regards, > Sven > > Am Donnerstag, 26. Mai 2016 12:21:15 UTC+2 schrieb Alex Miller: >> >> It's

[ANN] Clojure 1.9.0-alpha3

Clojure 1.9.0-alpha3 is now available. Try it via - Download: https://repo1.maven.org/maven3/org/clojure/clojure/1.9.0-alpha3 - Leiningen: [org.clojure/clojure "1.9.0-alpha3"] 1.9.0-alpha3 includes the following changes since 1.9.0-alpha2: - Macro fdef specs should no longer spec the implicit &f

Re: [ANN] Clojure 1.9.0-alpha3

The spec guide has been updated to reflect all changes as of alpha3: http://clojure.org/guides/spec On Thursday, May 26, 2016 at 9:05:54 AM UTC-5, Alex Miller wrote: > > Clojure 1.9.0-alpha3 is now available. > > Try it via > - Download: > https://repo1.maven.org/maven3/o

Re: clojure spec fdef

trying to provide useful feedback here, you all have done a > great job! > > Thanks, > Sven > > Am Donnerstag, 26. Mai 2016 14:53:13 UTC+2 schrieb Alex Miller: >> >> There is an example like this in the Sequence section and a bit on this >> issue in particular. >&g

Re: clojure spec fdef

I've tweaked that section of the doc to try to make that more explicit. On Thursday, May 26, 2016 at 10:12:43 AM UTC-5, Alex Miller wrote: > > I think the connection is that you are (always) describing function > arguments using regex ops. Maybe that could be made clearer. > &

Re: vector of chars vs string

On Friday, May 27, 2016 at 6:30:45 AM UTC-5, Camilo Roca wrote: > > If what I guess is right, the amount of chars that exist are finite, > Well, kind of - see Unicode. > thus Clojure treats them like a "pool of charts". > Java has a small number of primitive value types - byte, short, int, lo

Re: clojure.spec

On Friday, May 27, 2016 at 2:36:56 AM UTC-5, Pedro Pereira Santos wrote: > > Hello, > > How can I differentiate between the same keyword, but with difference > semantics? Example: > If you have different semantics, you should use different keywords (either different name or namespace). > >

Re: reader conditional not handling defmacro?

That is one option and is in the ballpark of http://dev.clojure.org/jira/browse/CLJ-1750. On Thursday, May 26, 2016 at 11:47:09 PM UTC-5, Nathan Davis wrote: > > I can't reply to the thread on the Dev list, but here's my take. > > Unless I'm missing something, it seems to me that most these issue

clojure.spec guide updated with generators

I've added a new section to the clojure.spec guide for generators. Certainly doesn't cover everything yet but hope it helps! http://clojure.org/guides/spec#_generators -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email

Re: vector of chars vs string

On Saturday, May 28, 2016 at 2:38:38 PM UTC-5, Camilo Roca wrote: > > @alex-miller > thanks, that explained a lot. I did check the UseStringDeduplication > feature and that's exactly what I was looking for. > > Funny thing is that it can only be implemented because string

Re: clojure.spec

There is a tutorial about spec in general at http://clojure.org/guides/spec On Saturday, May 28, 2016 at 8:39:27 PM UTC-5, Jiyin Yiyong wrote: > > > > Looking forward to tutorials~ -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group

Re: [ANN] Clojure 1.9.0-alpha4

Why? -- 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

Re: Vars named **

This was fixed in http://dev.clojure.org/jira/browse/CLJ-1233 way back in Clojure 1.6. On Saturday, June 4, 2016 at 5:25:34 PM UTC-5, Fluid Dynamics wrote: > > "Warning: ** not declared dynamic and thus is not dynamically rebindable, > but its name suggests otherwise. Please either indicate ^:dy

<    1   2   3   4   5   6   7   8   9   10   >