<DanC_>
I'm not confident I have the bandwidth to advocate it in the relevant forums, so I hope I can find a co-champion.
<DanC_>
SeanTAllen, any chance you're around to chat about this?
<doublec>
DanC_: I like the idea
<DanC_>
:)
<DanC_>
do you participate in the sync meetings and such?
<doublec>
I'm not sure how painful it will be passing ambient auth down to places where ffi is used though
<doublec>
eg. I often @printf[None](...) for debugging
* doublec
is a bad person :)
<DanC_>
ah... it's somewhat traditional to make an exception to this policy for logging/tracing. Perhaps I should add that.
<doublec>
But I remember reading a paper about Oz-e (which never eventuated) that warmed me on the idea.
Perelandric has quit [Ping timeout: 264 seconds]
<doublec>
DanC_: unfortunately the sync meetings clash with work meetings for me
<DanC_>
yeah...
* DanC_
added an item on logging/tracing under Unresolved questions 9794b89
amclain has quit [Quit: Leaving]
dynarr has quit [Quit: A merry Christmas to all, and to all a good night!]
Praetonus has quit [Quit: Leaving]
montanonic has quit [Ping timeout: 265 seconds]
montanonic has joined #ponylang
gsteed has joined #ponylang
DanC_ has quit [Ping timeout: 240 seconds]
DanC_ has joined #ponylang
montanonic has quit [Ping timeout: 244 seconds]
montanonic has joined #ponylang
c355e3b has joined #ponylang
montanonic has quit [Ping timeout: 258 seconds]
_andre has joined #ponylang
toblux has joined #ponylang
TwoNotes has joined #ponylang
<SeanTAllen>
DanC_: i was not around. i'm on US east coast, tend to go to bed early, rise early.
<TwoNotes>
It looks like there may be a fix for issue #1000. I wonder if there are other places that do _atomic operations that should be looked into?
<TwoNotes>
Or maybe some sort of test that really beats on those sections of the RT
runehog has quit []
jemc has joined #ponylang
jemc has quit [Client Quit]
jemc has joined #ponylang
toblux has quit []
<TwoNotes>
Need a test that forces the work-stealing code to run a lot.
<jemc>
TwoNotes: intuitively, to force lots of work stealing, I'd think you could do something like have an actor that makes a bunch of behaviour calls from a single central behaviour, but hogs its own scheduler thread
<jemc>
to hog its own scheduler thread, you could try doing "bad things" like a big `while` loop in you behaviour that makes a bunch of behaviour calls then calls `sleep` with FFI in each iteration :)
<jemc>
I'd think in that case that pretty much all of the work would get stolen
jemc has quit [Quit: WeeChat 1.4]
jemc has joined #ponylang
vrand has joined #ponylang
amclain has joined #ponylang
TwoNotes has quit [Quit: Leaving.]
jemc has quit [Ping timeout: 255 seconds]
jemc has joined #ponylang
Matthias247 has joined #ponylang
SilverKey has joined #ponylang
Praetonus has joined #ponylang
SilverKey has quit [Read error: Connection reset by peer]
montanonic has joined #ponylang
TwoNotes has joined #ponylang
Praetonus has quit [Quit: Leaving]
_andre has quit [Quit: leaving]
toblux has joined #ponylang
<lisael>
Hi, I've just posted a new issue on github, I had a segfault while benchmarking String