Re: cljs.test :after fixture not called if test errors

2020-11-24 Thread Estevo U. C. Castro
Try

(use-fixtures :once 
  (fn [f]
(println "before") 
(try (f) 
  (finally (println "after")

O mércores, 25 de novembro de 2020 á/s 00:17:03 UTC+1, 
stuart.will...@gmail.com escribiu:

> Hello,
>
> I'm experimenting with fixtures and it seems like :after fixtures aren't 
> run if a test unexpectedly errors. E.g.:
>
> (use-fixtures :once {:before #(println "before")
>  :after #(println "after")})
>
> (deftest a-test
>   (raise (js/Error. "oops")))
>
> In this example I expected to see "after" printed somewhere after the test 
> failed. Is this intentional?
>
> (I'm writing some tests for an Electron app using Spectron and want to 
> make sure the app is always shut down after the tests are complete.)
>
> Regards,
> Stuart
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/clojure/84dff1cf-6ea0-438c-a4c0-fac097223201n%40googlegroups.com.


Re: Clojure/flutter

2018-04-29 Thread Estevo U. C. Castro
This was apropos two points made in this thread:

- Clojure needing X from the runtime; my point here is that some Schemes 
may provide the things you'd demand from a native implementation: fast 
startup time, smallish binaries, etc., and even tail call optimization as a 
bonus, but also the drawbacks of a native implementation: mainly that you'd 
start with few libraries in comparison with the Java and JS implementations.

- A question about what would it take to make something like Clojurescript 
over again.  This implementation illustrates that you can reuse a lot of 
the work that was put into Clojurescript for new implementations.

IIRC this particular project petered out basically because the author 
didn't perceive much interest in this kind of thing from the Clojure 
community.  If that ever changes this project or something similar could be 
a good starting point for native-ish implementations.

domingo, 29 de Abril de 2018 às 03:56:27 UTC+2, Gregg Reynolds escreveu:
>
>
>
> On Sat, Apr 28, 2018 at 6:50 PM, Estevo U. C. Castro <eucc...@gmail.com 
> > wrote:
>
>> Just in case you hadn't heard of this:
>>
>> https://github.com/takeoutweight/clojure-scheme
>>
>> Thanks. Alas, most recent update seems to be 5 years ago. :(
>
> I know there have been some efforts along these lines but AFAIK they have 
> all petered out.  Anybody have the latest dope? 
>

-- 
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: Clojure/flutter

2018-04-28 Thread Estevo U. C. Castro
Just in case you hadn't heard of this:

https://github.com/takeoutweight/clojure-scheme

sábado, 28 de Abril de 2018 às 08:07:13 UTC+2, Didier escreveu:
>
> The thing about Clojure->native, is that Clojure needs a pretty powerful 
> runtime.
>
> So we'd need to piggy back on something native that similarly has a strong 
> runtime. Common Lisp maybe, or Go.
>
> I'd vote for Go.
>
>

-- 
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.