We are organizing some study meetings about Machine Learning in Clojure in
November.
Please use this questionnaire to tell us about your thoughts and
preferences:
https://twitter.com/scicloj/status/1319393868010369026
--
You received this message because you are subscribed to the Google
Groups
On Tue, Oct 20, 2020 at 2:19 PM Scott Klarenbach
wrote:
> Wondering who is living/working in Mexico City?
>
>
o/ Hey there!
Cheers,
Mauricio
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.
On Thu, Oct 22, 2020 at 12:00 PM EuAndreh wrote:
> Gregg Reynolds writes:
>
> > I could put that to good use, even if it isn't 100% "compliant". Is it
> > available?
>
> You can find the current WIP code here:
> https://git.euandreh.xyz/libedn/tree/src/core/rust
>
> Awesome, thanks!
--
You re
Ok great. If anyone is down for a beer in the sun to chat about tech,
programming etc let me know.
We've also got some contract work for Clojure devs on a pretty regular
basis if anyone is interested.
This is my company:
https://invisiblerobot.io
--
You received this message because you are su
Gregg Reynolds writes:
> I could put that to good use, even if it isn't 100% "compliant". Is it
> available?
You can find the current WIP code here:
https://git.euandreh.xyz/libedn/tree/src/core/rust
I'll announce on my website[0] once ready. Patches welcome.
Still missing:
- built-in tagged
On Fri, Oct 16, 2020 at 8:07 PM 'EuAndreh' via Clojure <
clojure@googlegroups.com> wrote:
>
> Hello there.
>
> I was working on implementing a specification compliant edn reader on
> Rust
I could put that to good use, even if it isn't 100% "compliant". Is it
available?
Thanks
Gregg
--
You r
Sean Corfield writes:
> Undefined behavior is deliberately very broad
I acknowledge the value of having undefined behaviour,
implementation-defined behaviour and unspecified behaviour in an
implementation, and I embrace that approach.
However, none of those are distinguished on the spec, which
James Reeves writes:
> Where in the specification does it say that the edn reader should throw
> exceptions on errors?
Well, it doesn't. I think had this expectation of forbidden things
throwing exceptions from some forbidden things throwing exceptions, and
some not doing so.
Both ":/" and ":/a
