01:07 <SeanTAllen> vaninwagen: i dont believe you can do that

08:04 <vaninwagen> I think so too, SeanTAllen, i think so too - i am spoiled by my scala day job - sugar everywhere

18:14 <notsgnik> hello everyone, I was wondering what happen when i run couple of behaviors and one of them did the job, can I cancel or kill the execution of the rest of the scheduled behaviors?

18:40 <SeanTAllen> no, you can't cancel behaviors. the message as been sent from one actor to another and it will be processed.

19:00 <notsgnik> hello SeanTAllen. So, if I run a file search who will run multiple behaviors to find the file. once it found it, the program will still keep searching?

19:04 <SeanTAllen> i dont know specifically what you are doing,

19:04 <SeanTAllen> behaviors cant be cancelled.

19:07 <notsgnik> There should be a way to cancel all behaviors scheduled by an actor. if i run a search over multiple databases and found my entry i should be able to cancel all the other searches, don't i?

19:17 <SeanTAllen> the performance costs of that at a runtime level would be very high and its a rather specific use case. you'll need to design something at the application level to handle that.

19:18 <SeanTAllen> behaviors are not scheduled. its a message send from one actor to another.

19:19 <SeanTAllen> actors are scheduled and they will process messages. messages are not scheduled. messages are not revokeable. if you want/need that, you could design it at the application level, but i think you will find its quite tricky.

19:21 <notsgnik> maybe a boolean ref that short circuit the behavior flow if the search is ended

19:21 <notsgnik> thanks for the help SeanTAllen :)

22:23 <olof> I just came across Pony and I really like it, I was sort of thinking of designing my own ideal language and was heading in a very similar direction (linear types to simplify the GC, union types, predicate dispatch), but Pony seems to be a generally much better and more fleshed out version of it

22:23 <olof> It's exactly the language I always wished for

22:40 <notsgnik> me to olof

22:42 <notsgnik> btw, it is normal that the random function giv the same numbers when i'm compiling and runing on my own computer?

22:42 <notsgnik> http://playground.ponylang.org/?gist=5e2b19ae9a897b7ac869e3e82496c6c4

23:02 <nisanharamati> @notsgnik You need to use a seed that will change between runs

23:02 <nisanharamati> https://playground.ponylang.org/?gist=44e63d4e1897ce2180d8e9d5552125d3

23:03 <nisanharamati> This is because the default values are always the same, and the random number generators are determinsitic for a given seed

23:43 <olof> Question, if I write code with higher order functions, like say map, what does the type of a function or lambda input look like? Lambdas are object literals iirc

23:48 <SeanTAllen> did you mean how do you indicate that a parameter is a lambda olof?

23:49 <olof> Yes, or some general function type

23:49 <SeanTAllen> here's an example method from Map in the standard library: `fun ref upsert(key: K, value: V, f: {(V, V): V^} box): V ?`

23:50 <SeanTAllen> f is a function that takes 2 values as parameters and returns a V

23:50 <SeanTAllen> for example: `m.upsert("test", 4, {(x, y) => x - y })`

23:50 <olof> ah ok, so {(input1type,input2type...) :outputtype}

23:51 <SeanTAllen> yes