03:22 <etc> Hi! I have a kind of strange problem where indentation in vim with both pony packages either places the cursor at the very beginning of the line or at some place far out in the middle of the line... is that supposed to happen? Has anyone encountered this before? Thanks!

03:45 <SeanTAllen> I haven't used the VIM package so I can't comment on that. Might want to try to mailing list. Probably more like to get a response there or by opening an issue on the vim plugin.

03:47 <etc> I'll make an issue - thanks!

03:53 <SeanTAllen> you're welcome.

06:31 <abbiya> i used pony deb from bintray and installed ponyc, but not able to do anything with it. illegal instruction (core dumped)

11:28 <SeanTAllen> abbiya_: that would probably be because your CPU doesn't support AVX or AVX2 instructions. We are working on a fix for that. If you build from source, you should be fine.

11:28 <abbiya_> ok, will try from the source

12:08 <thm> Hi. trying to use ponyc via rpm from bintray gives me "illegal hardware instruction (core dumped) ponyc"

12:09 <SeanTAllen> thm: that is probabl an AVX/AVX2 instruction issue. IE your CPU doesn't support. We are working on a fix for that . If you build from source, you should be fine.

12:10 <thm> ok, thanks

12:11 <SeanTAllen> sorry about that thm.

12:12 <thm> no problem. does the docker image have the same issue?

12:23 <SeanTAllen> it shouldn't, based on how it works.

12:24 <SeanTAllen> the current issue is related to the CI server the packages were built on having AVX and that having been picked up during the package build process. The coming fix will be to make the pre-packages binaries as basic and baseline as possible at the expense of some performance

13:29 <thm> the docker image is huge... and (as I expected) also shows the 'illegal instruction' problem. So I guess I'll have to build from source.

13:49 <SeanTAllen> jemc knows far more about the docker image than I. I've added that to the AVX issues to be addressed. thanks thm.

16:11 <etc> Hi! I'm trying to call a C function in Pony that requires passing in a pointer to a struct, and then reading from that struct later. So I made a tuple called Winsize and then have a value w = Pointer[Winsize]. This compiles but I'm unsure how to read the values from the tuple after passing it to the c function. Is this doable?

16:29 <SeanTAllen> etc, i have limited experience with C FFI. jemc and some others would be better to address. if you don't get an answer here, i'd try the mailing list. if you aren't around, you can check the IRC logs to see if someone answered later: http://irclog.whitequark.org/ponylang

16:31 <etc> (thumbsup) thanks I'll send an email if need be

17:10 <etc> I figured it out! If you're curious https://gist.github.com/Charlesetc/a97eb43d71a2e66d8a37705de5a375e3

17:24 <SeanTAllen> awesome!

17:25 <SeanTAllen> if you think the tutorial is lacking in that regard, PRs are greatly appreciated and encouraged etc

17:25 <SeanTAllen> Also, thank you again for noticing the lack of highlighting in the pony patterns

17:28 <etc> np! I'm working on a pr to add a bit about structs now :D

18:03 <SeanTAllen> etc: did you see the notice about the 2017 community survey?

18:13 <etc> Hmm taking a look now - anything in particular?

18:17 <SeanTAllen> nope. we did one last year. doing another this year. if the results are the same this year as last year for a lot of the questions, i'll mix it up next year.

18:17 <SeanTAllen> helps us get a handle on what the state of the community is etc

18:17 <SeanTAllen> there were a few things that surprised us last year

18:22 <etc> Yeah! I'm excited for the webdev and Pony for X parts

18:27 <SeanTAllen> sadly Pony for X hasn't really made any progress :(

18:27 <SeanTAllen> thm: btw, the AVX fix now includes a fix for docker issue as well... https://github.com/ponylang/ponyc/pull/1663/files. Thanks again for reporting.

19:22 <thm> thx for fixing this :)

19:25 <SeanTAllen> you're welcome

19:54 <thm> if I call two behaviours on an Actor, will these be serialized?

19:56 <SeanTAllen> thm: will what be serialized?

19:56 <SeanTAllen> do you mean

19:57 <SeanTAllen> if actor A sends messge foo and then bar to actor B

19:57 <SeanTAllen> will they be processed as foo then bar?

19:57 <SeanTAllen> if that is your question

19:57 <SeanTAllen> then yes

19:57 <SeanTAllen> there is casaul messaging

20:00 <thm> being totally new to pony, and inspired by a video) I experimented with this code: https://paste.fedoraproject.org/paste/760Ju3tvRkSvTqzCkP9rg15M1UNdIGYhyRLivL9gydE=

20:01 <thm> here, what is printed at the end, is totally indeterministic

20:04 <SeanTAllen> ues it should be

20:04 <SeanTAllen> s/ues/yes/

20:04 <SeanTAllen> you have 3 actors there

20:05 <SeanTAllen> the `inc` calls in `doit` are async

20:05 <SeanTAllen> there is no guarantee how many will be processed when `print` is called by `print`

22:20 <SeanTAllen> s

22:29 <etc> Is there an easier way to convert a u8 into a string? String.from_utf32(c.u32()).string()

22:43 <staticassert> I just installed the latest pony-release package (version 11) and I'm getting this error: http://pastebin.com/gHPzuZpz

22:44 <staticassert> Installed from here: https://bintray.com/pony-language/ponyc-debian/ponyc-release#files

22:57 <staticassert> I think it's possible that I had previously installed an old verison

23:00 <staticassert> Thinking it may be this: https://github.com/ponylang/ponyc/issues/1484

23:03 <staticassert> The --pic flag is mentioned as a solution in that thread but I had already tried it - same issue.

23:48 <SeanTAllen> staticassert: that's odd, can you open an issue for that?

23:51 <SeanTAllen> etc: in case you check the logs...

23:51 <SeanTAllen> https://www.irccloud.com/pastebin/LLQd2zUH/

23:54 <SeanTAllen> staticassert: nevermind it appears you already did

23:54 <staticassert> SeanTAllen: There was already an issue open that I found

23:54 <staticassert> I've commented on it. I can provide more information though - the full output of the error would probably be helpful. Will update soon.