Borrowing Safe Pointers from Rust in SPARK · HackerPapers discussions

Borrowing Safe Pointers from Rust in SPARK — mentioned by ajxs

Fri, 17 Apr 2026 11:26:04 GMT

The SPARK subset of Ada^1 has a similar kind of move semantics for pointer types^2. 1: SPARK is a formally verifiable subset of Ada: https://en.wikipedia.org/wiki/SPARK_(programming_language) 2: https://arxiv.org/pdf/1805.05576

Paper and discussion history. A mention is not an endorsement.

Borrowing Safe Pointers from Rust in SPARK — mentioned by MaxBarraclough

Sun, 29 Aug 2021 12:53:13 GMT

You might be interested in this thread from a year ago, where we discussed memory management in Ada. [0] The Ada folks sometimes seem a bit quiet on memory-management questions, a bit like the way Forth folks rarely talk about the real-world performance of Forth interpreters. On the plus side, borrower-checking is coming to SPARK. [1][2] [0] https://news.ycombinator.com/item?id=24361992 [1] https://www.adacore.com/papers/safe-dynamic-memory-managemen... [2] https://arxiv.org/abs/1805.05576

Paper and discussion history. A mention is not an endorsement.

Borrowing Safe Pointers from Rust in SPARK — mentioned by MaxBarraclough

Thu, 30 Jul 2020 17:55:24 GMT

It wasn't a mistake for Rust not to emphasise formal verification. Going that route would have been very restrictive. Rust is aiming to offer a safer alternative to C, not a more approachable formally verifiable language. That said, it looks like the good ideas from Rust may find their way into SPARK, a highly restrictive programming language for critical systems development with formal verification. [0][1] [0] https://www.adacore.com/papers/safe-dynamic-memory-managemen... [1] https://arxiv.org/abs/1805.05576

Paper and discussion history. A mention is not an endorsement.

Borrowing Safe Pointers from Rust in SPARK — HN submission

Mon, 27 Aug 2018 16:38:27 GMT

Borrowing Safe Pointers from Rust in SPARK

2 points; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.