I'll be more careful before posted code that doesn't compile :)
Anyway, here's my output using clojure 1.7-alpha3
https://lh4.googleusercontent.com/-MqiKnTcxneE/VFigwvQtzBI/A08/vGvY2waCJdc/s1600/Screen%2BShot%2B2014-11-04%2Bat%2B10.43.17.png
It could be that depending on OS/env the
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 every
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
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
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
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.
Looks cool, any design decisions that made you create this instead of using
honeysql https://github.com/jkk/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 foundation for
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
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
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))
The
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
best
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 []
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
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
Pardon my interruption: What are you using for screen output for your
roguelike?
On Tue, Oct 28, 2014 at 12:08 PM, Isaac Karth isaacka...@gmail.com wrote:
I've been working on some projects (roguelikes, story-generators) that
often have a reason to have a random outcome for things like
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
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 the
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
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
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 Google
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 Google
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
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 dsblakewat...@gmail.com wrote:
Pardon my interruption: What are you using for screen output for your
roguelike?
On Tue, Oct
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 mouse
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
Hi Daniel,
On Wed, Nov 5, 2014 at 3:06 PM, Daniel Marjenburgh dmarjenbu...@gmail.com
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
26 matches
Mail list logo
