10:11 <vaninwagen> does anyone know why there is no pow function/operator on the integer primitives in pony? or is there and i just didn't see it?

15:14 <SeanTAllen> i assume because previously folks would bitshift their way into that

15:20 <Candle> SeanTAllen: I suggest three options on https://github.com/ponylang/pony-stable/issues/22, which would be your preference? (if any!)

16:50 <SeanTAllen> commented Candle

20:51 <jemc> @cquinn: was working for real with the new `cli` package you wrote for the first time last night, and couldn't figure out how to create a CLI program that took only options, without needing a subcommand - is this not possible, or was I just missing something?

20:53 <jemc> as in, just creating a CLI program whose invocation looks like `myserver -p 9999` - when I tried to do so, I was getting "Error: missing subcommand at: 'myserver'"

20:57 <slfritchie> jemc I managed to do it in https://github.com/ponylang/ponyc/blob/master/examples/message-ubench/main.pony#L41-L57 ... but I confess I didn't know if it was proper use of the API or not.

20:58 <slfritchie> A faint memory says that the `ArgSpec.string_seq("", "")` in the third arg's array was needed. Or, rather, an empty array for the 3rd arg didn't work.

20:59 <jemc> hm, thanks for the clues - I'll investigate it further tonight :)

20:59 <jemc> if you managed it, then so can I :)

20:59 <jemc> (by looking at what you did, that is)

21:00 <jemc> I was a bit worried that it was impossible

21:00 <aturley> i'll second what slfritchie said. that's what i was coming up with when i was playing around with it.

21:01 <aturley> anybody else doing advent of code (https://adventofcode.com)?

21:01 <aturley> the problems are very simple. i'm using it as an excuse to explore parts of the pony standard library that i haven't looked at in a while.

21:04 <jemc> I think some of mycoworkers are doing it as an excuse to learn new languages

21:05 <SeanTAllen> sounds like we are definitely in need of better CLI docs

21:06 <jemc> it's possible that the empty-array-not-working behavior is an unintended bug, as the use-an-empty-argspec workaround is a bit ugly