Re: How to get Ada to “cross the chasm”?

["Dan'l Miller" <optikos@verizon.net>]

On Friday, May 4, 2018 at 11:13:09 AM UTC-5, guyclaud...@gmail.com wrote:
> Since this topic has somewhat turn into a Ada vs Rust/Haskell/whatever, could some experts show a piece
> of Ada code where the "borrower-checker" would more check/security ? Or are the paradigms too different
> to show a snippet close enough to (or IN ) Ada so that I can understand ?

The Ada source code that you are seeking (and corresponding Rust code) would demonstrate some form of utilization of the access keyword whose referent the borrow checker would track as either 1) mutably singly owned or 2) immutable shared.  As soon as the access keyword appears in source code, someone on c.l.a will say that a better memory-management design would be to either eliminate access altogether or bury it with a library.  Although I would applaud anyone who takes the time to craft such lucid demonstration Ada source code (as it would be illuminating to see variations on the theme), as soon as someone posts even a single line of Ada source code, there will be many replies that will conform to the 2nd sentence of this paragraph.  The main moral of the story (despite the quantity of the requisite back & forth replies) will tend to be the 1st sentence in this paragraph.

Ultimately it comes down to:  Rust's borrow checker in Ada would embrace accesses as much as references in Rust and smart-pointers in modern C++, but the trend of modern Ada is to de-emphasize accesses.  Ada-the-language and Ada-the-de-facto-culture are diverging over time.