jemc changed the topic of #ponylang to: Welcome! Please check out our Code of Conduct => https://github.com/ponylang/ponyc/blob/master/CODE_OF_CONDUCT.md | Public IRC logs are available => http://irclog.whitequark.org/ponylang | Please consider participating in our mailing lists => https://pony.groups.io/g/pony
khan has quit [Quit: khan]
khan has joined #ponylang
khan has quit [Quit: khan]
khan has joined #ponylang
khan has quit [Client Quit]
khan has joined #ponylang
khan has quit [Quit: khan]
khan has joined #ponylang
khan has quit [Client Quit]
khan has joined #ponylang
khan has quit [Client Quit]
khan has joined #ponylang
khan has quit [Client Quit]
khan has joined #ponylang
khan has quit [Quit: khan]
Pyrrh_ has joined #ponylang
khan has joined #ponylang
Pyrrh has quit [Ping timeout: 260 seconds]
Pyrrh_ is now known as Pyrrh
khan has quit [Client Quit]
khan has joined #ponylang
inoas has joined #ponylang
inoas has quit [Ping timeout: 268 seconds]
rurban has joined #ponylang
rurban has quit [Client Quit]
rurban has joined #ponylang
khan has quit [Remote host closed the connection]
rurban has quit [Client Quit]
inoas has joined #ponylang
acarrico has joined #ponylang
_andre has joined #ponylang
SenasOzys has quit [Ping timeout: 248 seconds]
SenasOzys has joined #ponylang
<vassilvk> Hi all! I have a question about issue labels. I'd like to contribute a PR to issue #1719, but I see it's labeled "bug: 0 - blocked". What does this label mean?
<SeanTAllen> vassilvk: it means something else has to be fixed before that issue can move forward
<SeanTAllen> what issue?
<vassilvk> #1719
dlowe has joined #ponylang
Mal__ has joined #ponylang
Mal__ has quit [Ping timeout: 260 seconds]
SenasOzys has quit [Remote host closed the connection]
<vassilvk> Any idea what's blocking it? I have a fix on my end -- building on an ARM64 system with no issues, all tests pass.
inoas has quit [Ping timeout: 264 seconds]
inoas has joined #ponylang
kempe has quit [Ping timeout: 260 seconds]
kempe has joined #ponylang
<SeanTAllen> Ah vassilvk
<SeanTAllen> it was blocked by not having anyone to test
<SeanTAllen> with am arm64 system
<SeanTAllen> so
<SeanTAllen> perfect!
<SeanTAllen> you are the unblocker!
<vassilvk> :)
<vassilvk> Sounds good -- PR coming soon
<SeanTAllen> sweet
khan has joined #ponylang
ybden has quit [Ping timeout: 265 seconds]
ybden has joined #ponylang
khan has quit [Quit: khan]
khan has joined #ponylang
khan has quit [Client Quit]
khan has joined #ponylang
acarrico has quit [Ping timeout: 268 seconds]
acarrico has joined #ponylang
brainproxy has quit [Quit: WeeChat 2.1]
acarrico has quit [Ping timeout: 248 seconds]
inoas has quit [Quit: inoas]
nisanharamati has joined #ponylang
acarrico has joined #ponylang
inoas has joined #ponylang
inoas has quit [Client Quit]
khan has quit [Quit: khan]
khan has joined #ponylang
khan has quit [Client Quit]
khan has joined #ponylang
khan has quit [Quit: khan]
khan has joined #ponylang
khan has quit [Client Quit]
khan has joined #ponylang
khan has quit [Quit: khan]
khan has joined #ponylang
brainproxy has joined #ponylang
<brainproxy> ^ where does _data.create() come from?
khan has quit [Quit: khan]
<slfritchie> brainproxy: It's from the left hand side of the equality on that same line
khan has joined #ponylang
<slfritchie> a bad generalization in pseudocode: let that_object: SomeType = that_object.constructor_call(args...)
<brainproxy> but the constructor is coming from where? from SomeType?
<slfritchie> Yes, the Map type.
<brainproxy> iow, _data wasn't defined previously, so how can we refer to its constructors
<brainproxy> i don't recall seeing that pattern in the ponylang tutorial or maybe I glossed over it
<brainproxy> seems like it would have been in the "Sugar" section
<slfritchie> `let` and `var` introduce variable definitions.
<slfritchie> So it's defined, on the left, then used on the right to call a constructor.
<slfritchie> (if that makes sense)
<brainproxy> sure, I can understand it, just didn't recall that pattern being explained
<brainproxy> no such example is given in Variables of Chapter 3
<slfritchie> Ah
<brainproxy> not a complaint, btw, just figuring things out, appreciate the help
<slfritchie> Hm, I don't see it in "Classes" in Chapter 2, https://tutorial.ponylang.org/types/classes.html
<brainproxy> I'm fairly certain the pattern isn't exhibited anywhere in the tutorial, I'll submit a GitHub issue
<slfritchie> brainproxy: Thanks for pointing this out
<slfritchie> I'm writing one up now
<slfritchie> Very nearly done....
<brainproxy> ah, okay, I'll stop writing then, just started :)
<brainproxy> looks good
<slfritchie> (I just fixed a typo in the title, silly me)
<slfritchie> Thanks for pointing out the omission
<slfritchie> If it is indeed mentioned somewhere, it's buried too deep. ^_^
<brainproxy> glad to help, very grateful for the tutorial, etc. and the helpful folks here in IRC
<brainproxy> I filed #282 yesterday, had just finished reading the tutorial and brought up the concern to Sean here in the channel
khan has quit [Remote host closed the connection]
<Bombe> I tried to set up a simple test but can not figure out from the documentation how to actually run it.
<Bombe> Does ponyc take some secret parameter to run the tests?
<slfritchie> Bombe: Are you trying to create a ponytest test case?
<Bombe> I believe so. I also think I found what I’ve been reading wrong. Let me try something.
<slfritchie> Perhaps this playground example can help? https://playground.ponylang.org/?gist=fb6c95f7ad4691f340e8bcd6b9eeafa1
<slfritchie> Oops, I didn't fix a cut-and-paste-o in the docstring for _TestTwo
_andre has quit [Quit: Lost terminal]
<SeanTAllen> Bombe: did slfritchie's answer help or where you already at that point and want to know how to run them?
<Bombe> Okay, got it. I missed the part where the tests are simply a second binary that needs to be built.
<slfritchie> Ok, good.
<Bombe> That also means that tests always need their own directories, right?
<slfritchie> I suppose you could add a command line flag or other signal that would run the unit test actor rather than the usual app main actor
<slfritchie> Ha, Sean and I were talking about that yesterday: which directory should test code go in?
<slfritchie> Both schools are feasible.
<SeanTAllen> we did that early on at Wallaroo Labs. We had meh results.
<Bombe> Heh. :)
<slfritchie> The Wallaroo repo puts tests into the same dir as code that it tests.
<SeanTAllen> Bombe, only if you have two Main functions, which generally isnt the case
* Bombe prefers separate tests.
<SeanTAllen> the "standard" in the standard library is that tests go in the directory with the code they are testing.
<SeanTAllen> jemc isnt fond of that
<SeanTAllen> i prefer the tests to be in the same package so you test private classes etc as well BUT...
<SeanTAllen> it does mean that any dependency of your package inherits the test dependencies as well which... sucks.
<SeanTAllen> definitely something i want to find a way to address.
<SeanTAllen> i have thoughts. people will probably hate them.
<Bombe> SeanTAllen, how do you run the tests when they’re in the same directory?
* Bombe is quite new in pony.
<SeanTAllen> well, in this case, its the only program in the directory, the rest is library code, so you can compile the _test.pony as a program and run it. or what we do is include the tests into one big test binary.
<SeanTAllen> but this for example, could be compiled and run to only run these tests: https://github.com/WallarooLabs/wallaroo/blob/master/lib/wallaroo/core/data_channel/_test.pony
<Bombe> Okay, but if I have an application I can not have two Main actors in one directory, right?
<SeanTAllen> correct
<SeanTAllen> it wont compile
<SeanTAllen> because there are two Main methods
<Bombe> So in that case I could: a) put the tests into a different directory, or b) put code and tests into a directory and only have a mostly-empty Main actor.
<SeanTAllen> i didnt follow option b
<Bombe> All code and accompanying tests go into one directory, and the “real” main class only contains a line like “App(env).start()”.
<SeanTAllen> yes that could work
<Bombe> Well, that should get me started, then. Thanks. :)
<SeanTAllen> you're welcome
nisanharamati has quit []
<jbk> i've been getting very familiar with the test framework this week :)
<jbk> as i chase down these last few bugs
<SeanTAllen> jbk: pony test?
<jbk> yeah -- i'm the one that's been porting it to illumos :)
<jbk> only 6 stdlib tests left
<SeanTAllen> ah
<SeanTAllen> welcome!
<jbk> hopfully i haven't been too annyoing on the dev list :P
<SeanTAllen> you have not
<SeanTAllen> i pointed praetonus at your LLVM question but he's been busy.
<jbk> the last 6 i suspect are probably all net/ failures, so it wouldn't surprise me if it's the same underlying problem causing them to fail
<jbk> just need to dig into them to see what's happening
<jbk> i went ahead and filed an issue -- the more i looked at the code, i'm pretty sure all the __digestof methods should have the same return type
<jbk> it just so happens w/ LP64 that for LLVM, they both happen to be i64
<jbk> but not ILP32
<SeanTAllen> sorry i cant be more help. i know the runtime really well and the compiler almost not at all.
<jbk> np
<SeanTAllen> sylvan and i joke that i know now the runtime better than him, so we'll have to do something to change that.
<jbk> i'm happy to dig and figure it out myself, but i also don't mind benefiting from the knowledge of others too :)
<jbk> so i figure it never hurts to ask
<SeanTAllen> indeed
<jbk> and really just doign this in my spare time, it hasn't been bad at all to port
<jbk> yay C :)
<SeanTAllen> i started at one point and then stopped. i did dragonfly because i needed something to do one day and porting to another OS is a mindless relaxing exercise for me.
<jbk> the biggest thing is just finding all the spots that needed updating
<SeanTAllen> indeed