08:44 <yorickpeterse> morning

08:48 <Benny1992> morning

15:09 <cremes> brixen: are you going to be at the ruby hack night at enova on oct 8? thinking of going into the city for it…

19:49 <brixen> cremes: if you're going to be there, I'll make a point of it :)

21:07 <cremes> brixen: i’ll know by that monday if I’ll make it. i’ll drop a note here as the day approaches.

21:44 <brixen> cremes: sounds good

22:01 <|jemc|> in general terms, when is the check_interrupts instruction required?

22:01 <yorickpeterse> |jemc|: whenever you're interrupted from working

22:02 <yorickpeterse> http://instantrimshot.com/audio/rimshot.mp

22:02 <|jemc|> the documentation for it says it "is used by loops", but is it the nature of a loop that requires it?

22:02 <yorickpeterse> * http://instantrimshot.com/audio/rimshot.mp3

22:03 <|jemc|> if one has a long-running method, but it contains no loops, should it be generating the check_interrupts instruction at regular intervals therein?

22:04 <|jemc|> and lastly, what are the consequences of not checking for interrupts - does it impede the JIT?

22:08 <|jemc|> I notice that it increments the call count for a method and thus is related to the JIT in that way (so that a method can be marked as heating up), but I'm really trying to ask if the intteruption is necessary so that the JIT can insert itself into that interruption do do its work before the code continues

22:10 <|jemc|> or if that is unrelated