Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify a couple points in the intro #529

Merged
merged 2 commits into from
Jan 30, 2024
Merged

Clarify a couple points in the intro #529

merged 2 commits into from
Jan 30, 2024

Conversation

SeanTAllen
Copy link
Member

Closes #348

@SeanTAllen SeanTAllen requested a review from a team January 28, 2024 19:34
@ponylang-main ponylang-main added the discuss during sync Should be discussed during an upcoming sync label Jan 28, 2024
@SeanTAllen
Copy link
Member Author

I fixed the build failure on the Netlify side.

docs/index.md Outdated
* It's data-race free. Pony doesn't have locks or atomic operations or anything like that. Instead, the type system ensures _at compile time_ that your concurrent program can never have data races. So you can write highly concurrent code and never get it wrong.
* It's deadlock free. This one is easy, because Pony has no locks at all! So they definitely don't deadlock, because they don't exist.

Pony can't stop you from writing logical bugs, but it can remove entire classes of bugs from being possible. The Pony compiler prevents you from unsafely accessing memory concurrently. If you've ever done concurrent programming, you know how hard such things can be to track down. With Pony, **poof**, don't worry about. Concentrate on "your logic". We think that makes Pony awesome and we hope you come to agree with us.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Pony can't stop you from writing logical bugs, but it can remove entire classes of bugs from being possible. The Pony compiler prevents you from unsafely accessing memory concurrently. If you've ever done concurrent programming, you know how hard such things can be to track down. With Pony, **poof**, don't worry about. Concentrate on "your logic". We think that makes Pony awesome and we hope you come to agree with us.
Pony can't stop you from writing logical bugs, but it can remove entire classes of bugs from being possible. The Pony compiler prevents you from unsafely accessing memory concurrently. If you've ever done concurrent programming, you know how hard such things can be to track down. With Pony, **poof**, don't worry about it. Concentrate on "your logic". We think that makes Pony awesome and we hope you come to agree with us.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Took joe's

docs/index.md Outdated Show resolved Hide resolved
Co-authored-by: Joe Eli McIlvain <joe.eli.mac@gmail.com>
@SeanTAllen SeanTAllen merged commit 7f037b8 into main Jan 30, 2024
5 of 9 checks passed
@SeanTAllen SeanTAllen deleted the issue-348 branch January 30, 2024 19:43
@ponylang-main ponylang-main removed the discuss during sync Should be discussed during an upcoming sync label Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clarify a couple intro points
5 participants