Re: About transients no longer being safe in 1.7-alpha2

Hi Daniel, On Wed, Nov 5, 2014 at 3:06 PM, Daniel Marjenburgh wrote: > My concern is purely about the safety that is taken away when transients > 'are' used wrongly. All the examples would've throw exceptions before > 1.7-alpha2, and they don't do so anymore. > > But they would run fine, if you

Re: About transients no longer being safe in 1.7-alpha2

Hi Alex, I understand any concurrent use of transients violates the usage expectations. Of course, if you treat any piece of mutable state sequentially like transients, you would not run into trouble either. My concern is purely about the safety that is taken away when transients 'are' used wro

Re: Deterministic Randomness in Functional Clojure

On Tuesday, November 4, 2014 9:54:39 PM UTC-5, Atamert Ölçgen wrote: > > clojure-lanterna is pretty cool. > > https://github.com/sjl/clojure-lanterna > > I'm interested in hearing about alternatives as well. > Terminal emulation? In this day and age? And a quick look around reveals no sign of mou

Re: Deterministic Randomness in Functional Clojure

clojure-lanterna is pretty cool. https://github.com/sjl/clojure-lanterna I'm interested in hearing about alternatives as well. On Wed, Nov 5, 2014 at 4:09 AM, blake wrote: > Pardon my interruption: What are you using for screen output for your > roguelike? > > On Tue, Oct 28, 2014 at 12:08 PM

Re: Neighbors function from The Joy of Clojure

Ouch! I found this code hard to understand. I read to previous part of the book. I guess it is normal when you are new to Clojure? -- 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

Re: Garden defcssfn not rendering

Ugh, just a case of RTFM. (css) needs a vector of CSS rules, so the following won't work (css (scale 2)) > The correct minimal test is: (css [:#testdiv {:transform (scale 2)}]) ;; "#testdiv {\n transform: scale(2, 2);\n}" -- You received this message because you are subscribed to the Goog

Re: Garden defcssfn not rendering

Ugh, just a case of RTFM. (css) needs a vector of CSS rules, so the following won't work (css (scale 2)) > The correct minimal test is: (css [:#testdiv {:transform (scale 2)}]) ;; "#testdiv {\n transform: scale(2, 2);\n}" -- You received this message because you are subscribed to the Goog

Re: Introducing Boot v2 with a streamlined CLJS workflow

Hi, sorry for the late reply! Boot pretty much takes care of that part for you, as long as you follow a few basic rules (I will be adding a “how to be a good citizen of the boot-o-sphere” section to the wiki on github soon): 1. Tasks don’t fish around in the filesystem directly to find thin

Re: Testing and infrastructure management for large Clojure app - how are you doing it?

Thanks Linus, You make a really good point - why can't testers use the REPL? I'd like to think that was possible too - after all, *I* can do it so why can't anyone else? That said, I'm slightly blessed in that I've done a lot of work in Erlang and R over many years, so I was already comfortab

Re: Testing and infrastructure management for large Clojure app - how are you doing it?

Thanks Colin I probably should've added that this is a large enterprise doing what's essentially an "in-house startup" - building an app using Clojure. The app initially sat somewhat "off to the side" of the corporation's main line of business, but there was always the intent to incorporate th

Re: Clojure usage in production - survey on Hacker News (Nov 2014)

I've added the list of companies using Clojure to clojure.org at http://clojure.org/Companies - feel free to ping me at alex.mil...@cognitect.com or here if you want something added/removed/changed. Alex -- You received this message because you are subscribed to the Google Groups "Clojure" gr

Re: Deterministic Randomness in Functional Clojure

Pardon my interruption: What are you using for screen output for your roguelike? On Tue, Oct 28, 2014 at 12:08 PM, Isaac Karth wrote: > I've been working on some projects (roguelikes, story-generators) that > often have a reason to have a random outcome for things like procedurally > generating

Re: OJ - A friendly way to talk to your database using Clojure.

It's funny, I actually didn't know about honeysql until today. When I found out that it existed, I got a little excited that someone else also came to the same conclusion independently. I think it says something good about this approach. As far as design decisions, I think OJ has a more minimal

Re: how clojure infers types.

The reason why that call doesn't require reflection is that Collection.unmodifiableSet has no overloaded methods, it only takes a Set so the compiler doesn't have to disambiguate between different signatures. Phillip Lord writes: > Yes, I checked the code. > > (defn set > "Returns a set of the

Re: how clojure infers types.

Yes, I checked the code. (defn set "Returns a set of the distinct elements of coll." {:added "1.0" :static true} [coll] (clojure.lang.PersistentHashSet/create (seq coll))) And that was my first assumption. But if clojure doesn't know the return type, then why does this: (defn two []

Re: [ANN] Arcadia, the integration of Clojure and Unity3D

The video linked here is different from the one in your Readme.md on github. This one works, the one in the Readme is broken (http://youtu.be/X4xCVsLhaZ0). On Friday, October 17, 2014 12:10:29 PM UTC-7, tims wrote: > > Arcadia lives at https://github.com/arcadia-unity/Arcadia. For now, the > be

Re: how clojure infers types.

Actually `set` and a lot of other clojure.core functions are neither inlineable nor have type hints. Phillip Lord writes: > I have a piece of code that looks like this > > (.getOWLEquivalentClassesAxiom > (owl-data-factory) > (set classlist) > (union-annotations classlist)) > >

how clojure infers types.

I have a piece of code that looks like this (.getOWLEquivalentClassesAxiom (owl-data-factory) (set classlist) (union-annotations classlist)) The method signature is getOWLEquivalentClassesAxiom(Set,Set) On runing lein check I get Reflection warning, tawny/owl.clj:2219:6

[ANN] Eastwood the Clojure lint tool version 0.1.5

Eastwood is a Clojure lint tool. It analyzes Clojure source code in projects, reporting things that may be errors. Installation instructions are in the documentation here: https://github.com/jonase/eastwood/#installation--quick-usage Updates since the last release are described in the chang

Re: OJ - A friendly way to talk to your database using Clojure.

Looks cool, any design decisions that made you create this instead of using honeysql ? On Tuesday, November 4, 2014 3:45:35 AM UTC+1, Taylor Lapeyre wrote: > > > > GitHub project link: > https://github.com/taylorlapeyre/oj > > The idea is to lay a solid foundatio

Re: Proof of concept: ClojureScript -> Apple's Javascript for Automation.

Could you please elaborate a bit about what you are trying to achieve? On Thursday, 30 October 2014 02:16:55 UTC+2, Daniel Szmulewicz wrote: > > This is a proof of concept to show how ClojureScript can be used in the > context of Apple's JavaScript for Automation that ships with Yosemite. > > ht

Re: About transients no longer being safe in 1.7-alpha2

I think all of these examples violate the usage expectations of transients (regardless of release) and you should expect to get confusing results from them. I do not think it's worth modifying core.async go blocks to do anything special in this regard (eince go is a macro I don't think you can

Re: About transients no longer being safe in 1.7-alpha2

Hi Daniel, On Tuesday, November 4, 2014 11:54:30 AM UTC+1, Daniel Marjenburgh wrote: > > Hi Jean, > > In this case, we are dealing with 1 key-value pair, so there is only one > transient reference all the time. It is not my experience that each update > returns a new transient value (here, each

Re: About transients no longer being safe in 1.7-alpha2

Hi Jean, In this case, we are dealing with 1 key-value pair, so there is only one transient reference all the time. It is not my experience that each update returns a new transient value (here, each update is identical to the original, as per the identical? predicate). I know you shouldn't use

Re: About transients no longer being safe in 1.7-alpha2

Hi there, On Tuesday, November 4, 2014 8:05:03 AM UTC+1, Daniel Marjenburgh wrote: > > I know transients aren't bash-in-place, as they may return new references, > but that is not the problem I'm having here. > If you bash in place, you would get unexpected results, but still the same > result e

Re: About transients no longer being safe in 1.7-alpha2

I'll be more careful before posted code that doesn't compile :) Anyway, here's my output using clojure 1.7-alpha3 It could be that depending on OS/env the seco