Re: {ANN} defun: A beautiful macro to define clojure functions with pattern match.

hi Dennis wow... that's beyond beautiful, it's awesome this makes Clojure even more 'Haskell-ish', which is a good thing in my opinion thanks for sharing this gem with the world Jay On Sunday, September 14, 2014 at 1:47:28 PM UTC+7, dennis wrote: > > > Hi , i am pleased to introduce defun

livecoding with Quil middleware

hello, i hope this is the place to discuss questions about Quil (i couldn't find a dedicated forum) and first of all, kudos to Nikita for this incredible library, which i find even better than the original Processing it's not just a matter of using a different syntax than java, but Nikita actua

Re: livecoding with Quil middleware

me, the second approach actually "remembers" original > version of fill-background. If you try changing that function it won't have > effect as interpreter no longer looks up function by name. > > I'm probably not explaining it very well but I hope it's sti

Re: livecoding with Quil middleware

are be > just a wrapper like it is now. > > On Wednesday, March 22, 2017 at 8:22:59 PM UTC-7, Jay Porcasi wrote: >> >> hi Nikita >> >> thank you so much for your explanation, it's very clear (and a bit >> surprising to learn that partial and anonymous

[QUIL] select-input and select-output?

hello, i'm looking for the Quil equivalents of Processing selectInput() and selectOutput() but i can't find them if they're not there, what would be the best way to directly access the corresponding Processing methods instead? or is there a different more convenient way to get the same function

Re: [QUIL] select-input and select-output?

thank you Nikita! i will try your example to understand it better a simple file chooser that returns the file path as string is all i need actually, i don't get all the complication in Processing of passing a callback function but i guess it must be there for a reason cheers, Jay -- You rece

Re: [QUIL] select-input and select-output?

ailable in quil by default thank you a lot for your help, Jay On Thursday, April 13, 2017 at 8:20:21 PM UTC+7, Jay Porcasi wrote: > > thank you Nikita! > > i will try your example to understand it better > > a simple file chooser that returns the file path as string is all i need

Re: [QUIL] select-input and select-output?

and gets 'compiled' (by a macro) to a plain middleware and Quil middleware functionality is pure genius On Monday, April 17, 2017 at 5:07:56 AM UTC+7, Nikita Beloglazov wrote: > > Glad to hear you worked it out. Feel free to contribute your > implementation of select-input/o

Re: [ANN] ClojureCUDA: a Clojure library for CUDA GPU computing

it sounds great, thanks Jay On Tuesday, April 25, 2017 at 6:33:49 AM UTC+7, Dragan Djuric wrote: > > I'll write more in an introductory blog post in a day or two. Until that, > there is a website http://clojurecuda.uncomplicate.org, that has the > details and documentation. > > It is similar to

hashmap keys

i would love to know in a bit more detail how Clojure manages to allow arbitrary data structures as keys for its immutable hashmaps hashing an atomic value as a string or number is fast and i see how that would work when atomic values are used as keys but how about using a big nested vector as a

Re: hashmap keys

thank you very much for the clarification so no magic there :-) using big nested structures as keys is gonna slow down things a bit but how caching can help? On Friday, November 10, 2017 at 12:29:41 PM UTC+7, tbc++ wrote: > > Most Clojure collections cache their hashcode, so that improves things

Re: hashmap keys

that was extremely instructive thank you very much! On Sunday, November 12, 2017 at 3:33:31 PM UTC+7, Gary Verhaegen wrote: > > Retrieving a value from a hashmap goes through the following steps: > > 1) Compute the hashcode of the supplied key. > 2) Navigate through the map's internal tree structu

Re: functional implementation of core.async primitives

wow looks so neat! i would be interested as well to know what experienced async users have to say Jay On Friday, November 10, 2017 at 1:32:52 PM UTC+7, Divyansh Prakash wrote: > > > Hi! > > I was messing around with Clojure and somehow ended up implementing a > functional > core.async clone <

Re: functional implementation of core.async primitives

interested to hear any feedback on these features On Wednesday, November 15, 2017 at 3:52:24 PM UTC+7, Divyansh Prakash wrote: > > Hi! > > Thank you for your feedback! > > I've made the following changes to my implementation : > - bounded channels with backpressure > - proper thread synchronizatio

Re: functional implementation of core.async primitives

keep it up, it's very interesting to follow Jay On Wednesday, November 22, 2017 at 2:52:46 AM UTC+7, Divyansh Prakash wrote: > > Just a follow up. > I have implemented parking versions of *!*, but (because I'm > not a sorcerer like *@halgari*) they are rather simple and not as > powerful as *cor