A simple new library for controlling a headless Chrome browser from Clojure
using the Chrome Devtools Protocol.
https://github.com/tatut/clj-chrome-devtools
All CDP commands are supported (as they are automatically generated from
the protocol specification by macros).
Also contains a rudimenta
Correct, this was just something Rich ran into while doing the pluggable
resolver work. The intent has always been that only aliases were to be
supported in auto-resolved keyword qualifiers and fully-qualified keywords
there would accidentally work. The spec and code now *only* support
aliases.
The breakage in CIDER is a good example of what this change disallows:
java.lang.RuntimeException: Invalid token: ::clojure.test/once-fixtures
Invalid because clojure.test is not an alias – so it should be
:clojure.test/once-fixtures instead (or ::test/once-fixtures). See the source
here:
http
>
> 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.
>
> Try it via
>
> -
Just for everyone's info: seems this update breaks CIDER
0.15: https://github.com/clojure-emacs/cider/issues/2081
--
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 m
To avoid confusion with Agile term “Scrum” the library, artifact and
namespaces were renamed to *Citrus* since v3.0.0. Older versions are still
available under the old name *Scrum*. To migrate to v3.0.0+ replace all
occurrences of *scrum* with *citrus.*
Old artifact name: *org.roman01la/scrum*
I usually model sum types as maps with either a :type or :tag key to
specify the kind of map it is. Occasionally, I use vectors with the tag in
the first position, especially when I need to favor concision, for example,
when the data is serving as a DSL with which I will be manually entering a
lot
Shot in the dark, but dependent namespace compilation may be the source of
your CLJS compiler slowdowns if you have tons of namespaces. Try seeing
what happens when you set :recompile-dependents to false in the CLJS
compiler options.
On Wednesday, August 23, 2017 at 11:54:44 AM UTC-4, Maarten T
Thanks, appreciated!
Compiling the CLJ side takes about 30 seconds, a non-optimized CLJS about
60 seconds, and an optimized CLJS about 120 seconds. I am very well aware
that these absolute numbers are not so high, at least compared to languages
such as Scala. However, I perform recompilations s
"My codebase (mix of CLJ, CLJS and CLJS) is about fifty thousand lines of
code, and compilation times are starting to interfere with my workflow
happiness. In addition, Chrome Devtools is becoming somewhat sluggish due
to the high number of separate namespaces loaded through Figwheel."
That's not
Clojure 1.9.0-alpha18 is now available.
Try it via
- Download: https://repo1.maven.org/maven2/org/clojure/clojure/1.9.0-alpha18
- Leiningen: [org.clojure/clojure "1.9.0-alpha18"]
1.9.0-alpha18 includes the following changes since 1.9.0-alpha17:
- Can now bind *reader-resolver* to an impl of Lis
Hi all,
My codebase (mix of CLJ, CLJS and CLJS) is about fifty thousand lines of
code, and compilation times are starting to interfere with my workflow
happiness. In addition, Chrome Devtools is becoming somewhat sluggish due
to the high number of separate namespaces loaded through Figwheel.
Just a casual bystander here, and this is fascinating to read. The
question screaming out to be answered is what problem are you trying
to solve with your choice of encoding? It seems both James and Timothy
have different requirements, both of which are valid but incompatible
with each other.
Noth
13 matches
Mail list logo