Pony (programming language): Difference between revisions

Revision as of 12:28, 11 January 2025

Revision as of 13:27, 11 January 2025

Line 31:

=== Safety ===

* Type Safety - Pony is a type safe language.<ref>https://www.ponylang.org/media/papers/fast-cheap.pdf</ref><ref name="hnoon"></ref>

* Memory Safety - There are no dangling pointers and no buffer overruns. There is no null but optional types can be safely represented using unions with the None type.{{Sfn|Allen|2024}}<ref name="atpony">{{cite conference |author=Ankush Thakur |date=21 December 2024 | title=12 New Programming Languages You Should Know| url=https://geekflare.com/dev/new-programming-languages/| access-date=3 January 20242025 |website=geekflare}}</ref>

* Exception Safety - There are no runtime exceptions. All exceptions have defined semantics and they are always caught.{{Sfn|MCStone|2023}}

* Concurrency Safety - The type system employs reference capabilities to ensure (at compile time) that your program is free of data races and deadlocks.{{Sfn|Mölle|2017}}<ref name="ipony">{{cite web |author=Sean T Allen |date=30 May 2018 |title=Introduction to the Pony programming language |url=https://opensource.com/article/18/5/pony |access-date=28 December 2024 |website=opensource}}</ref><ref>{{cite conference