Re: [ANN] Discontinuing 4clojure.com

Thanks for all the work (and money!) that's been spent over the years maintaining 4clojure, I know it's been much appreciated by many in the community. Is it possible to provide a data dump of the problem set? As far as I can tell this data isn't in the Github repo, it seems to be in a Mongo

Re: Inside Clojure Journal

I for one would appreciate it if you fixed it rather than removing it :-) On Wed, 30 Jan 2019 at 20:07, Alex Miller wrote: > That's never actually worked. I keep meaning to remove it. :) > > On Wednesday, January 30, 2019 at 1:41:16 PM UTC-6, puzzler wrote: >> >> +1. >> >> I can't seem to

Re: Prototype code for enhanced CIDER code completion for Java methods

oid. I think something as simple as > (String:charAt obj 0) notation would be pretty simple for a third syntax > (since we already have two built in ways of doing it) -- and closer to the > static method invocation syntax -- so really a third built-in syntax > (Integer/parseInt "12

Re: Prototype code for enhanced CIDER code completion for Java methods

Cursive already allows this with no syntax changes, but it does require reproducing Clojure's type inference in the editor. Cursive performs this type inference, so (modulo bugs) it knows the types of basically everything that the Clojure compiler does (and in fact in some situations can do

Re: [ANN] Clojure 1.10.0-beta1

> > I’m not sure a guide is needed for tap - the functions are pretty simple? > Personally, I understand the mechanics, but I have no idea how they're intended to be used. I'd love to see some examples of what they're designed to do. On Sat, 6 Oct 2018 at 12:17, Alex Miller wrote: > > > On Oct

Re: Unqualified symbol resolution during evaluation

Note that the doc on that page says: Note that class names normally denote class objects, but are treated > specially in certain special forms, e.g. . and new. > Basically, only a class makes sense as the first argument to new, and I suspect new doesn't use the standard symbol resolution. On

Re: [ANN] CRNTL: An ANSI C reader for Clojure/EDN content

That's really taking Friday afternoon commits to the next level! On 30 June 2018 at 21:42, Edwin Watkeys wrote: > Hey all, > > Have you ever wanted to read Clojure or EDN without using Clojure(Script)? > If so, feel free to check out CRNTL (C Reader for the Next Thousand Lisps) > at: > >

Re: [ANN] editscript: a diffing library for Clojure data

This looks very nice, thank you! On 1 May 2018 at 06:52, wrote: > Hello, > > I am happy to make available a diffing/patching library for Clojure data > structures. > > https://github.com/juji-io/editscript > > Two flavors of diffing algorithms are provided, with very

Re: Bazel as Clojure build tool

ourite language, but at least it's widespread which helps if you don't want to become an expert in it to just get your job done. On 15 April 2018 at 20:25, Gregg Reynolds <d...@mobileink.com> wrote: > > > On Tue, Jan 30, 2018, 6:07 PM Colin Fleming <colin.mailingl...@gmai

Re: [?] Adding my own function to clojure.core namespace

On 25 February 2018 at 23:42, Gary Fredericks wrote: > For clojure (not cljs, yet) I proxy all the dev utilities I might want to > use in a namespace called `.` so I can refer to it everywhere no matter > what the local namespace setup is: https://github.com/ >

Re: Bazel as Clojure build tool

Another tool that works well for polyglot JVM projects is Gradle. I use it to build Cursive, which has Java, Kotlin and AOT'ed Clojure. I released a mostly-unsupported plugin for it, and Andrew Oberstar and others have taken it over and done a lot of work on it - it now lives at

Re: Q: How to find out how much Clojure you use

IntelliJ has a nice Productivity Guide feature which works sort of like this - every time you use a certain feature it's recorded, and you can see a table of the various features, how often you used it and when you last used it. You can click on each feature to see documentation about how it

Re: [ANN] Automatically generate your specs and types

This looks great! Can this be used to infer macro specs based on examples of usage? On 14 October 2017 at 04:30, Ambrose Bonnaire-Sergeant < abonnaireserge...@gmail.com> wrote: > Hi, > > Happy to announce a new set of tools to *automatically* > *generate* types and specs for your projects. > >

Re: SourceDebugExtension Class Attribute in clojure-1.8.0.jar

The other thing that would be affected is debugging using a bytecode debugger like Cursive's - that won't work without the debug info in the bytecode. pack200 is usually something that you'd use for deployment though, so perhaps this isn't a problem. On 12 October 2017 at 23:39, Alex Miller

Re: [ANN] JMH-Clojure: Seamless JMH benchmarking for Clojure

This looks really fantastic - thank you! I've used JMH recently and it's definitely awkward to use - I'll use this next time for sure. On 29 September 2017 at 09:24, wrote: > A data-oriented API to JMH > , the Java >

Re: Is it wrong that I'm thinking about this?

I'm pretty sure you can't use a bare colon - Clojure will attempt to read it as a keyword and will fail since there's nothing following. :- is just a normal keyword. I think you can take the minimalist syntax too far, if there were no separator at all then you'd have to be counting elements to

Re: Writing an Android application with Clojure

Kotlin offers a lot more than just less verbose code and fixing quirks. It's a sufficiently large step up over Java that the experience of using it is completely different, in my experience. The null-safe type system is worth the price of entry alone. I totally recommend it for Android projects.

Re: [ANN] Clojure 1.9.0-alpha18

> > Tighten autoresolved keywords and autoresolved namespace map syntax to > support *only* aliases, as originally intended What does this mean? Is there a JIRA discussion about this? On 24 August 2017 at 04:03, Alex Miller wrote: > Clojure 1.9.0-alpha18 is now available.

Re: [ANN] Insn: Functional JVM bytecode generation for Clojure.

This looks very interesting. How would you compare this to Mage for the CLR? Are they essentially equivalent? On 19 August 2017 at 11:49, wrote: > Insn is a data-oriented API to the ASM JVM bytecode > generation library. It also provides additional

Re: CHAMP an improvement on HAMT?

Previous discussion from Zach Tellman about his CHAMP implementation (bifurcan): https://groups.google.com/d/topic/clojure/1m_I7IrDGb0/discussion It seems that Clojure's hashing and in particular equality semantics are relatively expensive, and this accounts for most of the performance

Re: Reducing Jar file size for AWS Lambda

portkey looks great, I wasn't aware of that - thanks! On 23 July 2017 at 20:35, Kimmo Koskinen wrote: > Hi! > > Although still at early stages, check out portkey > https://github.com/cgrand/portkey. > > Portkey does tree-shaking by starting from a closure to minimize

Re: Migrating nREPL out of Clojure Contrib

> > Are you saying the contrib process is deliberatly made to be difficult for > the community to contribute to it? No, not at all, just that it's deliberately designed to be exactly the way it is, so dedicating a lot of time to trying to change that is likely to be frustrating and fruitless. I

Re: Migrating nREPL out of Clojure Contrib

> > I'd much rather see nREPL stay within contrib and the renewed effort, that > you propose, to go into ironing out kinks in the contrib process FWIW I don't think this is a realistic option, certainly not for anyone outside of Clojure core. The contrib process is in place because some want it

Re: Migrating nREPL out of Clojure Contrib

I don't have much more to add than what others have written - I don't have very strong feelings about this, but it seems worth fixing if the contrib process is a significant barrier to contribution. And if that happens, I agree with Chas that it seems worth taking the time to reboot it properly,

Re: slackpocalypse?

On 24 May 2017 at 00:13, Herwig Hochleitner wrote: > I doubt the whole community would want to move anywhere from Slack. > Perhaps this will have to wait until Slack inevitably throws us off, then. What would you need to solve your discoverability issues (a)? Isn't it

Re: slackpocalypse?

There's been a lot of discussion around this, there's a page about the possibility of moving to Matrix here: https://hackpad.com/The-case-for-Matrix-xRXYSO9zpyh. While it has some nice properties (decentralised, open, can be encrypted etc) it comes at a serious usability cost. I doubt the whole

Re: [ANN] huffman-keybindings 0.0.1

Hi Edouard, This library is indeed interesting. However one comment (without wanting to derail the conversation from the library itself) - the use of AGPL is likely problematic since Clojure and the majority of the libraries available for it use the EPL. See here

Re: [ANN] Clojure 1.9 / clojure.spec split

Doesn't this mean that Clojure and spec will be mutually dependent, i.e. a dependency cycle? Is that likely to cause problems for any tooling? On 27 April 2017 at 06:27, Sean Corfield wrote: > Whilst this is rather disruptive for current users of clojure.spec, I > understand

Re: Derefs broken after clojure.tools.namespace.repl/refresh

Yes, that's correct. On 12 April 2017 at 17:56, Didier wrote: > @Colin If I understand correctly, if I buy the personal license I can use > it for my own commercial projects, but I can also use it at my work, to > work on their code base, as long as I'm the one using it. Is

Re: Derefs broken after clojure.tools.namespace.repl/refresh

;> >> Am I living in the past? I thought Clojure didn't have a way to step >> through code interactively? >> >> On Tuesday, 11 April 2017 16:30:14 UTC-7, Colin Fleming wrote: >>> >>> A good debugger is indeed extremely useful for Clojure - I use one every

Re: Derefs broken after clojure.tools.namespace.repl/refresh

A good debugger is indeed extremely useful for Clojure - I use one every day :-) On 12 April 2017 at 05:29, Didier wrote: > Experimentation is good. This is indeed surprising. I think it shows that > a good debugger would still sometime be useful in Clojure. I can't really >

Re: was Re: ANN: Orchestra, complete instrumentation for clojure.spec

> > I have longed for a statically compiled language with type inference with > the simplicity and consistency of Clojure's syntax that also supports > generative testing and works on the JVM but alas, I have not found one. > Frege and PureScript both look interesting but I am unsure of Frege's >

Re: Compiling gen-class runs static initializers: workarounds, solutions?

Ah yes, I remember this now. It seems like this is a fix that would definitely help, too, since many (most?) people using serious interop will be type hinting. On 28 March 2017 at 23:15, Adam Clements wrote: > Potentially relevant? I posted a patch two years ago for

Re: Compiling gen-class runs static initializers: workarounds, solutions?

I believe this is fixed in Clojure 1.7, see http://dev.clojure.org/jira/browse/CLJ-1315 for lots of detail. On 27 March 2017 at 08:51, lonign via Clojure wrote: > Hi David, > > It's been a long time, but have you found a solution to this problem? I > came across a

Re: java interop, `(.instanceMember Classname)`

I commented over there too - I'm still confused. On 22 March 2017 at 10:59, Alex Miller wrote: > > > On Tuesday, March 21, 2017 at 11:43:25 AM UTC-5, John Gabriele wrote: >> >> >> Erf. Sorry. I don't think I understand that after all, and as well may >> have confused

Re: java interop, `(.instanceMember Classname)`

Object doesn't have a getName() method. This doc is confusing - as Phill comments above, this is calling the getName() method on an instance of Class. In Clojure, a bare classname (String, ArrayList or whatever) resolves to the class itself if it has been imported (i.e. what would be String.class

Re: No :out in my nREPL responses

ich worked fine. > I don't think my issue has anything to do with Cursive's way of connecting > to nREPL, but rather with nREPL itself, seeing as had the same problem in a > terminal window running `lein repl`. > > Terje > > > On Friday, March 17, 2017 at 2:11:11 AM UTC

Re: No :out in my nREPL responses

Hi Terje, When you say the "standard" REPL in Cursive, are you referring to the "Use nREPL in normal JVM process" option, or the "Use clojure.main in normal JVM process" option? Obviously the first does use nREPL, but doesn't go through lein - Cursive just runs a JVM process, starts a bare-bones

Re: ANN: ClojureScript 1.9.456, Externs Inference & Comprehensive JS Modules Support

I believe that dependency is because Google Closure requires it. On 9 March 2017 at 16:45, Mike Rodriguez wrote: > Guava is often a dependency conflict when trying to put libs together that > use it. I'm surprised cljs has dependencies like this. I'd think a language > would

FYI: Eclipse Aether moved to Apache Maven

Hi all, I just saw a notice about this on the Aether mailing list today, and it potentially affects some of us building tooling (especially Leiningen/boot/pomegranate etc). Aether has been developed under the Eclipse umbrella until recently, but as far as I could tell had been almost totally

Re: Clojure.spec, maps, restrict valid keywords, easier way?

I'm actually planning to do exactly that in Cursive, and it's more or less what Eastwood does too per the link Ben posted. On 4 February 2017 at 14:23, Linus Ericsson wrote: > It would be great if an editor highlighted a (possibly qualified) keyword > that was used

Re: Cyclic namespace dependencies!

As a counterpoint to this, note that ClojureScript does the same thing (for different reasons, but the same mechanism): https://github.com/clojure/clojurescript/blob/master/src/main/clojure/cljs/core.cljc#L91-L101 On 1 January 2017 at 05:24, Timothy Baldridge wrote: > Be

Re: Kotlin null-safety in Clojure?

I wrote about this a bit on the ML recently: https://groups.google.com/d/msg/clojure/Dxk-rCVL5Ss/NqF-Na9ABQAJ TL;DR - you really need types for this, and it's very difficult to add types to a Clojure-like language without losing what makes it Clojure. In particular, if you want to maintain Java

Re: [ANN] An exploration of Hash Array Mapped Tries

Hi Ambrose, This looks very interesting, and I look forward to investigating it further when I have a moment. Once comment on the defrecords generated at runtime based on small keysets - I'd be very careful with this sort of optimisation, and it needs much more than micro-benchmarks to establish

Re: Clojure as a first programming language?

On 5 December 2016 at 02:56, 'Lee Spector' via Clojure < clojure@googlegroups.com> wrote: Colin Fleming has done some nice work on this in Cursive. > Sadly that work is not in Cursive proper yet, although I'm planning to get it in there soon once I work out what I'm doing with spec.

[ANN] gradle-clojure 1.1.0

Hi all, I've just published 1.1.0 of gradle-clojure, a Gradle plugin for compiling Clojure code and running tests. You can find it at https://github.com/cursive-ide/gradle-clojure. Changes in this version are support for JUnit XML test report generation thanks to Piotrek Bzdyl, and also support

Re: Java like static typing for Clojure?

Yes, that is a major selling point. Generative testing is really cool, and you should definitely not be disheartened - it's a tool like any other, with its strong points and weak points (like static typing, too). It's definitely not universally applicable, and even more than standard testing, it

Re: Java like static typing for Clojure?

> > On 21 October 2016 at 18:40, Colin Fleming <colin.mailingl...@gmail.com> > wrote: > > I tried it a couple of years ago, and my impressions were more or less > the > > same as CircleCI's here. I found the type annotation burden much higher > than > > usin

Re: Java like static typing for Clojure?

must not be nil and that any Java > method may return nil. > > On Thursday, October 20, 2016 at 8:39:04 AM UTC-4, Colin Fleming wrote: >> >> I recently spent a bunch of time researching exactly this. My motivation >> was that my main project, Cursive, suffers from a to

Re: Java like static typing for Clojure?

containing nil) are > reported earlier and better (because they occur at the point they are > introduced rather than later and several layers down in some RT method). > > On Friday, October 21, 2016 at 10:15:23 AM UTC-5, Colin Fleming wrote: >> >> This is a discussion that I'v

Re: Java like static typing for Clojure?

This is a discussion that I've had a couple of times. I don't think that interop is the main factor here, I think it's more that I'm programming against a large codebase I don't understand well (I can't since it's around 4 million LOC). I suspect that if I were programming against a large

Re: Java like static typing for Clojure?

I recently spent a bunch of time researching exactly this. My motivation was that my main project, Cursive, suffers from a ton of NPEs which I find very difficult to manage. I wanted to see how difficult it would be to have a typed Clojure-like thing, using something similar to Kotlin's type

[ANN] gradle-clojure 1.0.1

Hi all, I mentioned to several people that I’ve been using a Gradle plugin I wrote to compile Cursive. I’ve just published it here: https://github.com/cursive-ide/gradle-clojure. It’s also in the Gradle plugin repo. It’s currently very basic, but it works for what I need. If anyone needs extra

Re: Two suggestions re: core.spec, `ns`, and clojure 1.9alpha11

is to make Clojure more approachable (hence the obsession with error messages), so I'm glad it's helped your co-workers! And you never know, maybe you'll like it enough one day to switch :-) On 26 August 2016 at 21:15, Rick Moynihan <rick.moyni...@gmail.com> wrote: > On 26 August 2016 at 0

Re: Two suggestions re: core.spec, `ns`, and clojure 1.9alpha11

it works. On 26 August 2016 at 20:24, Alex Miller <a...@puredanger.com> wrote: > On Thursday, August 25, 2016 at 9:11:39 PM UTC-5, Colin Fleming wrote: >> >> >> One thing that I think would help a lot would be if it were possible to >> show the actual text from t

Re: Two suggestions re: core.spec, `ns`, and clojure 1.9alpha11

Hi Rick, That looks really excellent, and is a huge improvement. Particularly in combination with Leon's proposed change which more precisely identifies the likely failing part of the grammar, this looks like a big win for not much extra effort. One thing that I think would help a lot would be

Re: Two suggestions re: core.spec, `ns`, and clojure 1.9alpha11

ead. > > But I'm not a moderator, so I guess take whatever I say with a grain of > salt. :) > > On Thursday, August 25, 2016 at 7:12:04 PM UTC-4, Colin Fleming wrote: >> >> I really don't understand how you expect anyone to take your criticism >>> seriously if

Re: Two suggestions re: core.spec, `ns`, and clojure 1.9alpha11

> > I really don't understand how you expect anyone to take your criticism > seriously if you keep implying you're happily abandoning the language for > greener pastures. > Why would anyone developing Clojure look at anything you have to say at > this point as anything less than trolling?

Re: Two suggestions re: core.spec, `ns`, and clojure 1.9alpha11

This is almost exactly the intuition behind the standard error reporting heuristic for grammars involving alternations. It is a heuristic, but it has to be since on a failure it's impossible to entirely accurately determine the user's intention. But intuitively, generally the rule that has managed

Re: Two suggestions re: core.spec, `ns`, and clojure 1.9alpha11

:require thing comes from the way that novices > confuse the ns macro with the function that pulls dependencies in at the > REPL. Cutting / pasting between the REPL and the file can allow that to > bleed in. I know it confused me. > > On Wednesday, 24 August 2016 01:09:48 UTC+2

Re: Two suggestions re: core.spec, `ns`, and clojure 1.9alpha11

other channels about the "learning to read" error >> messages part and I think you've taken it entirely the wrong way or maybe I >> just disagree. There are benefits from reporting errors in a generic, >> consistent way. […] >> >> >> Do there exist

Re: Two suggestions re: core.spec, `ns`, and clojure 1.9alpha11

ng way or maybe I >> just disagree. There are benefits from reporting errors in a generic, >> consistent way. […] >> >> >> Do there exist examples of what is desired for error messages in >> 1.9-final? Not promises, but a “this is what we’re shooting for”? What >> wo

Re: Two suggestions re: core.spec, `ns`, and clojure 1.9alpha11

he cases that everyone will encounter all the time, particularly new users trying to figure out the language syntax. On 23 August 2016 at 12:55, Alex Miller <a...@puredanger.com> wrote: > > On Monday, August 22, 2016 at 7:43:53 PM UTC-5, Colin Fleming wrote: >> >> I agree that the a

Re: Two suggestions re: core.spec, `ns`, and clojure 1.9alpha11

I agree that the ability to get a machine-readable parse failure is very important for tooling. However I feel very strongly that the error messages that are printed by default on macro validation failures should be easily understandable, and the current ones are not. If we completely punt to

Re: Two suggestions re: core.spec, `ns`, and clojure 1.9alpha11

I think there's considerable scope to produce better error messages automatically than what spec produces, and I hope that can happen for 1.9. The error message produced by the code I demoed at the conj last year would be: Unexpected symbol 'require' at while parsing namespace clauses. Expected

Re: Two suggestions re: core.spec, `ns`, and clojure 1.9alpha11

With respect to preserving undocumented behaviour, while in general I'm in favour of making compilers stricter, in this case it seems like the change breaks a lot of existing code in ways that are impossible for library consumers to fix themselves - they have to wait for an update to the library,

Re: [ANN] Clojure 1.9.0-alpha11

> > (ns ... (require ...) (import ...) ) instead of (ns ... (:require ...) > (:import ...) ) Is this not intended to be allowed? The docstring implies no but it has always worked fine - I wouldn't call the code broken. Does the spec also limit the refs to

Re: Multi-OS Engine | Intel(R) Software

Looks like MOSE uses Android's ART (from https://software.intel.com/en-us/node/633226): Multi-OS Engine Runtime is based on the modern Android ART*, which is the > runtime component of Android that runs Java apps. > ART has a list of features that provide optimal performance for apps on > iOS

Re: Implementing a generic parameterized Java interface so that it satisfies (instance? ParameterizedType)

es, it might be > possible to implement those interfaces as well. There's probably a way to > do this in pure Clojure. > > On Thu, Aug 4, 2016 at 4:55 PM, Colin Fleming <colin.mailingl...@gmail.com > > wrote: > >> Hi Jakub, >> >> Yes, that is correct - Clojure int

Re: Implementing a generic parameterized Java interface so that it satisfies (instance? ParameterizedType)

Hi Jakub, Yes, that is correct - Clojure interop only deals with raw classes, it has no concept of generics. Java is the way to go here. Cheers, Colin On 5 August 2016 at 09:28, Jakub Holý wrote: > I need to implement the interface javax.websocket. >

Re: [ClojureScript] ANN: The REPL, a weekly Clojure/Script newsletter

Thanks for The REPL, I've been enjoying it very much. I like that it also has information related to Clojure but not Clojure-specific, such as JVM performance posts. Nice work! Cheers, Colin On 27 July 2016 at 09:20, Daniel Compton wrote: > Hi folks > > I’ve

Re: [ANN] Nightcode 2: Total Rewrite

What I do for Leiningen in Cursive is basically mimic what the lein script does, and download the uberjars to .lein/self-installs, and then run processes with those on the classpath. Would something similar for Boot work? As I understand it, boot.sh is just a tricky wrapper around an embedded jar,

Re: [ANN] Clojure 1.9.0-alpha8

Is there a JIRA with details on the namespaced keyword changes? On 29 June 2016 at 11:48, Leon Grapenthin wrote: > This is fantastic. Spec really seems to turn out like a "killer-feature" > for Clojure. > > On Wednesday, June 29, 2016 at 12:13:25 AM UTC+2, Alex Miller

Re: more minimal clojurescript intro/app

Hi Lee, Here's another recent interesting post: http://blog.klipse.tech/clojure/2016/06/07/klipse-plugin-tuto.html. This looks like it might be very useful for you. Cheers, Colin On 12 June 2016 at 11:03, 'Lee' via Clojure wrote: > > Just an update on this and

Re: Deep transients

<mark.engelb...@gmail.com> wrote: > That's an interesting idea. Maybe there's a way to build a set of Specter > navigators that operate on transients, and then use its corresponding > eqiuvalences for assoc-in, update-in, etc. > > On Thu, Jun 2, 2016 at 9:01 PM, Colin Fl

Re: Deep transients

Have you looked at Specter? I actually don't know if it uses transients under the hood or not, or if you can make it do so, but it seems like a good fit for the data manipulation problem, at least. On 3 June 2016 at 14:43, Mark Engelberg wrote: > Let's say I have an

Re: [ANN] Clojure 1.9.0-alpha1

I'll also need a spec translator (from s/form or s/describe, I guess - I'm not clear on the difference), and I'm very interesting in seeing any details if someone gets to it before I do. Cheers, Colin On 25 May 2016 at 12:38, Timothy Baldridge wrote: > The output of

Re: CCW stopped working. How do I fix it?

On 5 May 2016 at 00:46, Fluid Dynamics wrote: > Doesn't cursive (or its host) cost money and emacs cost gray hairs? > Cursive is free but not OSS for non-commercial use, and it works fine with the IntelliJ community edition, which is Apache licensed OSS. > Also, nothing

Re: Simple memory usage tuning for clojure

As would I - I've used YourKit a bit but the results can often be pretty impenetrable. Also, knowing how to interpret results specifically for Clojure would be great too. Jonathon, if you're specifically interested in memory, check out Eclipse MAT - it's a great, free tool for analysing heap

Re: Porting Clojure to Native Platforms

April 2016 at 23:47, Stig Brautaset <s...@brautaset.org> wrote: > Colin Fleming <colin.mailingl...@gmail.com> writes: > > > Unit of compilation is the module, not sure how that all plays out > with > > the Elixir repl, but it's not optimal. From what I can

Re: Porting Clojure to Native Platforms

> > Unit of compilation is the module, not sure how that all plays out with > the Elixir repl, but it's not optimal. From what I can tell, re-deffing a > defn would require re-loading an entire namespace (module)... > Reloading a whole namespace on an evaluation doesn't seem like a

Re: Porting Clojure to Native Platforms

Of course, most people using Lua seriously use LuaJit, which is surprisingly fast. However it's very prone to the branching problems you described earlier for complex application code. I believe LuaJit does optimise hashmaps when they're used as arrays etc. LuaJit really shines when used for

Re: Porting Clojure to Native Platforms

This is true of a lot of those benchmarks, especially for functional languages. I haven't looked recently, but back in the day Haskell seemed very fast on the shootout game. However the code that actually runs that fast is very very far from idiomatic. Again, I haven't looked at the Clojure

Re: more minimal clojurescript intro/app

In terms of learning a minimum about how ClojureScript itself works, I'd recommend starting from the Quick Start . It uses no external tooling so there's no house of cards effect which can be discouraging for new users. You'll end up with

Re: Clojure as first language

Have you come across any *new* programmers who think in terms of bit twiddling? I agree with Mark - this tends to be intuitive once you've learned that that is all there is. This might have been the case long ago when people started programming by learning about how CPUs work, but computers are so

Re: Which GUI toolkit would you like to see wrapped in an idiomatic Clojure library?

That sounds great Timothy, thanks! On 18 March 2016 at 06:32, Timothy Baldridge wrote: > It uses the same sort of logic that React does. Fn-fx creates a virtual > dom, and then diffs the previous virtual dom against the updated one. From > there you get a list of necessary

Re: Including debugging information for Clojure code

d at those sources briefly, but now I >> won't spend time on them. >> >> -James >> >> On Monday, March 14, 2016 at 2:26:11 AM UTC-4, Colin Fleming wrote: >>> >>> I don't have much time right now, but AFAIK Cursive is the only debugger >>>

Re: Including debugging information for Clojure code

I don't have much time right now, but AFAIK Cursive is the only debugger using JDI - CIDER has a source manipulation debugger. I don't generally have to do anything special to debug, although I use an IntelliJ layer on top of JDI. I can try to check if it's doing anything with that flag. You can

Re: [ClojureScript] Re: Clojure Google Summer of Code 2016 - Submit your project ideas!

That's a shame. Was any feedback given? On 1 March 2016 at 10:05, Alex Miller wrote: > Unfortunately, we were informed today that Clojure was not selected as a > 2016 Google Summer of Code organization. :( > > > On Thursday, February 18, 2016 at 3:47:59 PM UTC-6, David

Re: [ANN] Doubling down on Onyx

Hi Michael, Congratulations! That's fantastic - I'm really happy to see more people being able to work full time on tools :) Cheers, Colin On 25 February 2016 at 05:22, Michael Drogalis wrote: > Hi everyone, > > I'm happy to announce that, starting next week, I'll be

Re: [ANN] dali SVG library 0.7.0

This looks really lovely, thanks! On 11 February 2016 at 13:51, Stathis Sideris wrote: > ...aaand the link to the repo: https://github.com/stathissideris/dali > > > On Thursday, 11 February 2016 00:49:54 UTC, Stathis Sideris wrote: >> >> Hello all, >> >> dali is a Clojure

Re: Splitting Read into 2 steps?

Hi Terje, This is how the parsing works in Cursive. I have a classical lexer/parser split because IntelliJ forces me to do that. That said, I like it that way, and I believe it makes things more flexible. I've been able to make a couple of special-case parsers easily on top of the lexer - I'm

Re: Scala/Clojure/F# - Functional Programming Advocates - New York/Chicago/San Fran

Just this afternoon I was looking at the HN Who's Hiring thread for February. 621 comments there, mostly job postings with the occasional question comment, so perhaps 500-550 actual postings. 15 postings mention Clojure, with 9 being what looks like

Re: Clojure beyond Java 6 ?

> > Such project obviously don't care about bug fixes and new features, since > they are stuck with dangerously old legacy JVM versions anyways, which is > both a security risk, a risk of added defects, and prevents usage of newer > Java features. > Sigh. I feel like a broken record here, but

Re: Reducing the pain of a clojars outage

I'm travelling at the moment so I don't have time to respond to everything right now, but one thing about the Java 6 issue - IntelliJ won't be fully on Java 8 until IntelliJ 16. This means that Java 6 will be around until a) everyone is on whatever comes after El Capitan (the last OSX to support

Re: [ANN] pex, a powerful PEG parsing library

I'm really impressed by how fast it is out of the box with basically no optimisations. Tatu Saloranta is fanatical about Jackson performance, getting to within 6x on the first attempt is very promising. On 20 November 2015 at 02:43, Ghadi Shayban wrote: > Thanks for taking a

Re: deprecation warnings?

Sadly Cursive doesn't show this right now - it definitely should, though. Cheers, Colin On 15 October 2015 at 06:55, William la Forge wrote: > *warn-on-deprecated* would be super! :D > > On Wed, Oct 14, 2015 at 1:44 PM, Alex Miller wrote: > >> You

Re: Using metadata to specify how calls to a macro should be indented

Unfortunately as tools developers we can't force our indentation preferences on our users, although I'd be fine with it if you convinced everyone to just use two spaces for everything, even though it's not my preferred formatting. Cursive has supported this for ages (copied from Emacs) but I don't

Re: Using metadata to specify how calls to a macro should be indented

This is an interesting proposal, and I like it in general. Everything in Cursive is based on extensions identified by the head form, like this: (style/register-formatting :clojure.core/def :only-indent) (style/register-formatting :clojure.core/defn- :only-indent) (style/register-formatting

Re: Cursive and gen-class

On 25 August 2015 at 18:22, Fluid Dynamics a2093...@trbvm.com wrote: I seem to recall criticizing a piece of Clojure-relevant *technology* that had the rather remarkable property that it could be working, be deleted and reinstalled (exact same version), and suddenly be *not* working. Except

  1   2   3   4   >