EDIT: ...for the development of dynamic web applications.
On Tuesday, December 18, 2018 at 8:31:25 PM UTC-8, Christopher Small wrote:
>
>
> Hi Juraj
>
> Glad you have it working now!
>
> I mostly use oz from the Clojure REPL as an exploratory tool in my work on
> Polis (see
Great to hear. Thanks for checking it out!
On Tuesday, December 18, 2018 at 10:38:12 AM UTC-8, Alan Thompson wrote:
>
> Looks very nice. I will definitely be using this in the future.
> Alan
>
>
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To
Hi Juraj
Glad you have it working now!
I mostly use oz from the Clojure REPL as an exploratory tool in my work on
Polis (see https://www.youtube.com/watch?v=2tBVMAm0-00). I have yet to use
the Reagent API in a dynamic front end, but I have used Vega & Vega-Lite in
a vanilla React app (see
No, I'm not saying that - the reason I was looking at cause was due to some
gnarly exception check messages for compiling Clojure code. I'm not sure
that these are applicable in general. Given that this is not what the
original case was, I think we should set that aside for now.
Going back to
Alex, just so I understand, are you saying that because of the
implementation of `(is (thrown-with-msg? ..))` and the changes to
exceptions in Clojure 1.10.0, that other Clojure programs that use `(is
(thrown-with-msg? ...))` may need to be updated to use something similar to
what you linked, in
Hi folks
In the last ten years or so, source code formatters with limited/no
configuration have become popular. Go is the most well-known example,
shipping with gofmt, but there are similar tools in Rust, JavaScript,
Python, and Elixir.
Clojure and Lisps, in general, have historically allowed
And the macro which that test case exercises can be found here:
https://github.com/Engelberg/instaparse/blob/dcfffad5b065e750f0f5835f017cdd8188b8ca2e/src/instaparse/core.cljc#L274
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group,
And to be as specific as possible, the actual test that worked in 1.9 but
not in 1.10 is:
https://github.com/Engelberg/instaparse/blob/dcfffad5b065e750f0f5835f017cdd8188b8ca2e/test/instaparse/defparser_test.cljc#L34
I've temporarily elided the test from the instaparse test suite, but wanted
to
Sorry, I tried to "shrink the error case" and I appear to have gone too
far. The actual problem would be more like:
=> (is (thrown? AssertionError (eval (quote (f true
On Tue, Dec 18, 2018 at 11:11 AM Alex Miller wrote:
> Oh, if you're testing with thrown-with-msg?, that definitely can
Hi Chris and Boris,
Thanks for the quick response.
Here's the minimal example: https://github.com/jumarko/oz-sample
It looks like a dependency conflict with something in my
~/.lein/profiles.clj
If I run it via `lein repl` it fails.
If I run it only with proflie then it works!
lein with-profile
Oh, if you're testing with thrown-with-msg?, that definitely can have an
impact due to the nested exception. In clojure.test, I'm using a variant to
test the message with the root cause:
https://github.com/clojure/clojure/blob/master/test/clojure/test_helper.clj#L134-L151
On Tuesday, December
Looks very nice. I will definitely be using this in the future.
Alan
On Tue, Dec 18, 2018 at 4:44 AM wrote:
> Odd. The exact same code works for me. This is clojure 1.10/oz 1.4, and
> evaluating the whole blob from lighttable.
>
> I had to call (oz/v! line-plot) again to get it to show the
Leiningen monkey patches clojure.test so I tend not to trust it for repros.
> On Dec 18, 2018, at 12:05 PM, Andy Fingerhut wrote:
>
> I do not know if Leiningen is involved in the difference in the reproduction
> project linked below yet (I am testing with the latest Leiningen 2.8.3 here),
>
Hi Juraj
The code you pasted *should* work. If you're still having trouble with
this, please raise a GH issue with all pertinent system/setup details so we
can sort it out there: https://github.com/metasoarous/oz/issues.
I can say that sometimes it takes a while for the websocket connection to
I do not know if Leiningen is involved in the difference in the
reproduction project linked below yet (I am testing with the latest
Leiningen 2.8.3 here), but I do see a clojure.test `(is (thrown-with-msg?
...` expression that gives no error when running 'lein test' with Clojure
1.9.0, but does
Great stuff!
(btw, I had to "brew install graphviz" on mac first to make it work)
I looked at your tools.deps.alpha usage and I think you're fine on what
you're using. I have thought about the api a lot and when we move out of
alpha, I will try to make that clearer. Certainly, any public vars
Clojurians-1.10.0:
I recently released a small project that allows you to view the entire
dependency graph of your deps.edn files. You can do this from the command
line without installing anything or adding anything to your project.
https://github.com/cnuernber/depsviz
To do this, I had to
If you are a mac user, clj on brew has been updated to default to 1.10 now.
brew upgrade clojure
On Monday, December 17, 2018 at 11:30:01 AM UTC-6, Alex Miller wrote:
>
> Clojure 1.10 focuses on two major areas: improved error reporting and Java
> compatibility.
>
>
> Error reporting at the
Thanks to everyone who designed, implemented, and tested this release!
On Tuesday, December 18, 2018 at 5:33:07 AM UTC-5, Rick Moynihan wrote:
>
> Great news,
>
> Thanks to everyone who made this possible!
>
> R.
>
> On Tue, 18 Dec 2018 at 09:02, Thomas >
> wrote:
>
>> Thank you for this
In particular, I am challenging this assertion from the original post:
However, the following test (using is from clojure.test) used to work prior
to 1.10, but now fails:
=> (is (thrown? AssertionError (f true)))
Unexpected error (AssertionError) macroexpanding f at
This particular example given fails in a similar way on 1.9. Could you give
me something closer to what you are actually seeing in your test suite?
Specifically something that is a passing clojure.test test on 1.9 but a
failure/error on 1.10?
The problem with the given example is that it
I think the relevant change here is that exceptions thrown during
macroexpansion are now wrapped into CompilerExceptions as a way to attach
all of the source context information. The REPL understands this and still
prints the original cause so the printing hides some of that structure (but
you
Odd. The exact same code works for me. This is clojure 1.10/oz 1.4, and
evaluating the whole blob from lighttable.
I had to call (oz/v! line-plot) again to get it to show the figure, rather
then the opening text. And you can leave out the (oz/start-plot-server!). It
will start a server if it
Great news,
Thanks to everyone who made this possible!
R.
On Tue, 18 Dec 2018 at 09:02, Thomas wrote:
> Thank you for this release and all the hard work everyone has put into
> this!!!
>
> Thomas
>
> On Monday, 17 December 2018 18:30:01 UTC+1, Alex Miller wrote:
>>
>> Clojure 1.10 focuses on
Agreed. It is not a problem for functions which throw AssertionErrors,
only macros. But this is a change in behavior which breaks test suites
which passed previously.
On Tue, Dec 18, 2018 at 1:48 AM alex wrote:
> I'm not sure, but probably it behaves so because of throwing at
> macroexpand
I'm not sure, but probably it behaves so because of throwing at macroexpand
stage.
вторник, 18 декабря 2018 г., 11:29:09 UTC+2 пользователь puzzler написал:
>
> Consider the following macro:
>
> (defmacro f [x] {:pre [(number? x)]} `(+ ~x 5))
> => (f 3)
> 8
> => (f true)
> Unexpected error
I'd like to try this but got stuck pretty early:
(ns clojure-repl-experiments.visualizations.oz
(:require [oz.core :as oz]))
(oz/start-plot-server!)
(defn group-data [& names]
(apply concat (for [n names]
(map-indexed (fn [i x] {:x i :y x :col n}) (take 20
(repeatedly
Consider the following macro:
(defmacro f [x] {:pre [(number? x)]} `(+ ~x 5))
=> (f 3)
8
=> (f true)
Unexpected error (AssertionError) macroexpanding f at
(test:localhost:62048(clj)*:265:28).
Assert failed: (number? x)
So, as expected it throws an AssertionError if passed a non-number.
However,
Thank you for this release and all the hard work everyone has put into
this!!!
Thomas
On Monday, 17 December 2018 18:30:01 UTC+1, Alex Miller wrote:
>
> Clojure 1.10 focuses on two major areas: improved error reporting and Java
> compatibility.
>
>
> Error reporting at the REPL now categorizes
29 matches
Mail list logo
