<vaninwagen>
tbillington yeah, the httpget example is a full blown cli app - better have a simple example that shows the basic plumbing
MuffinOfPrey has joined #ponylang
notsgnik has joined #ponylang
samuell has joined #ponylang
samuell has quit [Ping timeout: 258 seconds]
guest5081 has joined #ponylang
<guest5081>
hmm, considering how Pony's traits/interfaces work, could they in theory support automatic delegation like Kotlin? ( https://kotlinlang.org/docs/reference/delegation.html ) I.e. automatically delegating the methods of a trait to one of your class fields
samuell has joined #ponylang
guest5081 has quit [Remote host closed the connection]
MuffinOfPrey has quit [Quit: Leaving]
mollymorphic has joined #ponylang
mollymorphic has quit [Ping timeout: 258 seconds]
notsgnik has quit [Ping timeout: 240 seconds]
<SeanTAllen>
i dont see the connection guest5081. the kotlin example seems to be inheritance based. perhaps i'm not reading it correctly?
mollymorphic has joined #ponylang
mollymorphic has quit [Ping timeout: 240 seconds]
bimawa has joined #ponylang
notsgnik has joined #ponylang
acarrico has joined #ponylang
samuell has quit [Remote host closed the connection]
bimawa1 has joined #ponylang
bimawa2 has joined #ponylang
bimawa has quit [Ping timeout: 248 seconds]
bimawa_ has joined #ponylang
bimawa3 has quit [Ping timeout: 240 seconds]
bimawa1 has quit [Ping timeout: 248 seconds]
samuell has joined #ponylang
olof has joined #ponylang
gokr has quit [Ping timeout: 268 seconds]
olof has quit [Ping timeout: 240 seconds]
olof has joined #ponylang
notsgnik has quit [Ping timeout: 240 seconds]
profetes has joined #ponylang
jemc has joined #ponylang
acarrico has quit [Ping timeout: 240 seconds]
olof_ has joined #ponylang
olof has quit [Ping timeout: 258 seconds]
olof_ is now known as olof
acarrico has joined #ponylang
olof has quit [Ping timeout: 248 seconds]
gokr has joined #ponylang
jemc has quit [Ping timeout: 268 seconds]
mollymorphic has joined #ponylang
vaninwagen has quit [Ping timeout: 268 seconds]
jmiven has quit [Quit: co'o]
jmiven has joined #ponylang
mollymorphic has quit [Ping timeout: 248 seconds]
acarrico has quit [Ping timeout: 268 seconds]
mollymorphic has joined #ponylang
dougmacdoug has joined #ponylang
guest5081 has joined #ponylang
mollymorphic has quit [Read error: Connection reset by peer]
samuell has quit [Quit: Leaving]
gokr has quit [Ping timeout: 240 seconds]
mollymorphic has joined #ponylang
user10032 has joined #ponylang
endformationage has joined #ponylang
samuell has joined #ponylang
dougmacdoug has left #ponylang [#ponylang]
nisanharamati has joined #ponylang
user10032 has quit [Quit: Leaving]
user10032 has joined #ponylang
mollymorphic has quit [Ping timeout: 248 seconds]
mollymorphic has joined #ponylang
acarrico has joined #ponylang
<endformationage>
Perhaps a nice addition to the logger package would be a TestLogger, which instead of printing to an OutStream, prints to the test helper's log.
<endformationage>
This way, libraries which incoporate logging can have their messages grouped in test runs, as per the test helper's log fun
jemc has joined #ponylang
<endformationage>
Ah, I see Outstream is in interface, perhaps I can hook this up..
acarrico has quit [Ping timeout: 268 seconds]
jemc has quit [Ping timeout: 248 seconds]
<endformationage>
Found something similar to what I needed in the logger package tests. Here is my OutStream replacement passed to Logger construction in tests:
<endformationage>
Might it be useful for the test helper to offer such a stream?
_andre has quit [Quit: leaving]
<SeanTAllen>
I'm not sure what the purpose is, I've read what you wrote a couple times endformationage, but I'm not really understanding.
<endformationage>
SeanTAllen: Sorry for the lack of clairity. I've integrated logging from the logging package into a library I'm writing. It's useful to see these logs also durring test runs.
<endformationage>
However they are interleaved in the test output as on can imagine with concurrent tests being run.
<endformationage>
Thankfully the test helper offers log()
<endformationage>
I wanted to hook up my integration of a `Logger` to the test helper logging facility, and found this could be achieved by creating an actor that structuraly subtypes OutStream.
<endformationage>
... and I pass an instance of this, a `TestHelperLogStream` to the Logger[String] I give to my library in tests.
<endformationage>
The result is the logging is collected under each test, and also works nicely with the --verbose option provided by the ponytest package.
<endformationage>
I thought perhaps it'd be useful for the ponytest TestHelper to offer an instance of something like the TestHelperLogStream for this use case.
gokr has joined #ponylang
mollymorphic has quit [Ping timeout: 248 seconds]
mollymorphic has joined #ponylang
jemc has joined #ponylang
benq has joined #ponylang
mollymorphic has quit [Ping timeout: 248 seconds]
mollymorphic has joined #ponylang
mollymorphic has quit [Ping timeout: 248 seconds]
mollymorphic has joined #ponylang
stephen has joined #ponylang
stephen is now known as Guest94121
Guest94121 has quit [Quit: Page closed]
nisanharamati has quit []
user10032 has quit [Quit: Leaving]
mollymorphic has quit [Ping timeout: 248 seconds]
mollymorphic has joined #ponylang
notsgnik has joined #ponylang
<SeanTAllen>
that sounds interesting endformationage
user10032 has joined #ponylang
user10032 has quit [Remote host closed the connection]
notsgnik has quit [Ping timeout: 248 seconds]
<endformationage>
SeanTAllen: Did I clear up the confusion I made? Hehe, I am terrible at simplifying sometimes and am always very 'wordy'. :/