Add blog post: Pony's Errors Stop Unwinding the Stack#1340
Merged
Conversation
a410309 to
481a0d9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a blog post about the coming change to Pony's error handling: replacing stack unwinding with error-flag returns. It covers the aarch64 segfault that pushed me to do it — the one Joe, Sylvan, and I came to believe is a bug down in LLVM — the years we'd spent circling the idea, the branch-predictor reasoning behind it, and what the new mechanism does.
The change itself is ponylang/ponyc#5002, still in review, so the post is written for what's coming: present tense for how Pony works today, the new mechanism framed as the change. Publishes 2026-05-26 at 2:30pm ET.