09:17 <travis-ci> dipinhora/ponyc#517 (cbs - a61eeb1 : dipinhora): The build was fixed.

09:17 <travis-ci> Change view : https://github.com/dipinhora/ponyc/compare/a4f0b8b7b630...a61eeb1a294b

09:17 <travis-ci> Build details : https://travis-ci.org/dipinhora/ponyc/builds/460657778

09:38 <mwm-pony> Wow, what a gauntlet to connect to FreeNode!

09:40 <mwm-pony> I am interested in writing a pony implementation of blake2. Does this seem like something which should be in the stdlib given its usage in package signatures? Or should I not concern myself with that for now?

09:41 <mwm-pony> I have already done and Elixir implementation, so I don't think it's outside of my capabilities.

09:47 <vaninwagen> It would make a great fit for the crypto package in stdlib

09:48 <mwm-pony> Cool. Is there a good place to read about how to contribute in the least intrusive way?

09:55 <mwm-pony> Just any sort of conventions which will make it less likely I waste anyone's time

10:12 <vaninwagen> I would suggest to make it work as a separate package outside stdlib first, and then issue an RFC for inclusion in stdlib

10:13 <vaninwagen> There is the style guide for code style: https://github.com/ponylang/ponyc/blob/master/STYLE_GUIDE.md

10:14 <vaninwagen> And there is this project to as a suggestion on how to set up a pony package: https://github.com/ponylang/library-project-starter

10:14 <mwm-pony> Excellent, thanks.

10:15 <vaninwagen> For issueing the RFC: https://github.com/ponylang/rfcs/blob/master/README.md

10:15 <vaninwagen> I would love to see a small benchmark on your blake2 implementation using ponybench: https://stdlib.ponylang.io/ponybench--index

10:16 <vaninwagen> I can also help with that

10:18 <mwm-pony> I'll undoubtedly be a while getting it all together properly.

10:18 <mwm-pony> I'm happy to do the benchmarking and such once I get it together. And hopefully learn how to make it better!

13:41 <_andre> is there a public roadmap for pony?

13:45 <vaninwagen> Not at this moment, but i would welcome if there was one

14:04 <SeanTAllen> _andre: that would be hard given that pony is a volunteer project and we don't have a structure like say Mozilla and Rust where we can say "and now we are going to have these people that we are paying work on X"

14:04 <SeanTAllen> if there are particular areas you are interested in, I can tell you if I have heard of anyone working on that area.

14:04 <SeanTAllen> I can also tell you what I think is important, what Sylvan thinks is important based on conversations with him.

14:41 <_andre> SeanTAllen: i meant it in an "informational" way, so that users know what's being worked on

14:41 <_andre> i find that sort of thing interesting, but i understand people could start demanding things from the developer team

14:42 <_andre> personally, the only thing i miss so far is the exhaustiveness verification in matches, and the "newtype" feature would be nice to have

15:18 <SeanTAllen> i'd love to see both of those as well

15:18 <SeanTAllen> neither is something i'd be good at implementing at this time

15:18 <SeanTAllen> i know the runtime really well

15:18 <SeanTAllen> i'm rather poor in the compiler department at this point in time

18:29 <travis-ci> ponylang/pony-stable#341 (master - 1ccfd30 : Benjamin Pellittieri): The build was broken.

18:29 <travis-ci> Change view : https://github.com/ponylang/pony-stable/compare/9474403f7f2d11cfdd8fa00b85b1961038e4d214...1ccfd3077e80bcd2a7ef49820ac814bc055229da

18:29 <travis-ci> Build details : https://travis-ci.org/ponylang/pony-stable/builds/460909499

19:00 <travis-ci> ponylang/ponyc#5488 (master - 5fc1b04 : marsuk): The build was broken.

19:00 <travis-ci> Change view : https://github.com/ponylang/ponyc/compare/fa3e302f751f3b2cd32f4aaf7f1d52dafa97ad8f...5fc1b04ca78b050cdf6d5f7a630d878a705a5710

19:00 <travis-ci> Build details : https://travis-ci.org/ponylang/ponyc/builds/460909544

19:15 <vaninwagen> It seems llvm 3.9 just became unavailable for trusty: Removing ponyc-build-deps:amd64 because I can't find llvm-3.9:amd64

19:16 <vaninwagen> http://apt.llvm.org seems to confirm this

19:17 <vaninwagen> Fixing our issues with llvm > 3.9 just became a little more pressing

19:33 <SeanTAllen> Ummm

19:33 <SeanTAllen> why do we need it for trusty?

19:33 <SeanTAllen> what's using it?

19:34 <SeanTAllen> Also sadly it doesn't appear to be available in our hosted llvm dependencies which is bad: https://github.com/ponylang/ponyc-llvm-dependencies

19:35 <SeanTAllen> in the future, we need to make sure anything we are using like that has a backup in the llvm dependencies

19:46 <vaninwagen> I cannot check today but gonna have a look tomorrow

19:48 <SeanTAllen> at least know we know and can add more stuff using git-lfs to that llvm dependencies repo.

20:51 <haarts> Silly question; I want to print to stdout from one of my classes. Do I need to pass the Main actor's `env`?

20:51 <aturley> haarts you could pass the `out` object from `env`.

20:51 <aturley> or you could use `Debug`.

20:53 <haarts> yeah, it is actually regular operation I want. So passing the `out` object is the best solution?

20:54 <aturley> haarts that's probably better than passing the whole env.

20:55 <haarts> thanks for the help!

20:55 <aturley> you're welcome