Skip to content

Last Week in Pony - April 29, 2018

Last Week In Pony is a weekly blog post to catch you up on the latest news for the Pony programming language. To learn more about Pony check out our website, our Twitter account @ponylang, or our Zulip community.

Got something you think should be featured? There’s a GitHub issue for that! Add a comment to the open “Last Week in Pony” issue.

We need you

We could use help moving Pony forward. Interested in helping? Here’s a few ideas:

And there’s a ton more as well. Stop by the developer mailing list, we’ll help you figure out a way that you can contribute.

Items of Note

  • Detecting end of incoming actor messages discussion on /r/ponylang. Got anything to add? Join in. Also, this question has come up before. We’d love to see someone write up a Pony Pattern for addressing this scenario.

  • Work is underway to vendor LLVM into Pony. As you might know, the only version of LLVM listed as support by the Pony team is LLVM 3.9.1. LLVM 5 and 6 are experimental only. Why? LLVM 5 and 6 have bugs that we need to get fixed. All-in-all, our current LLVM support story isn’t working out well. During the April 18th Pony developer sync call, we decided that we needed to support a single version of LLVM that we could patch and periodically upstream. This would make Pony’s LLVM usage a lot more like the model used by Rust. Interested in helping with the effort? Wink has been working on the effort for a while. Stop by his pull request and see how you might assist.

Pony Development Sync

The Pony developers met on their weekly sync call on Wednesday, April 25, 2018. Check out the recorded audio.

The next one is scheduled for Wednesday, May 2, 2018, at 03:30 PM (GMT-04:00) America/New York via zoom. We’d love to have you there.


Interested in making a change, or keeping up with changes to Pony? Check out the RFC repo. Contributors welcome!

Approved RFCs