Re: Microsoft is considering moving to Rust; potential opportunity for Ada2020

["Alejandro R. Mosteo" <alejandro@mosteo.com>]

On 8/8/19 4:13, Jere wrote:
> On Wednesday, August 7, 2019 at 5:09:06 AM UTC-4, Alejandro R. Mosteo wrote:
>> On 6/8/19 19:49, Brad Moore wrote:
>>
>>> I believe it is also not just related to concurrency. For example, if you pass a pointer to an object into a function which deletes the object, the compiler will detect that use of that pointer after calling the function is not allowed.
>>
>> Yes; concurrency safety (in a limited sense) is the side-effect, not the
>> main point, I'd say.
> 
> I think at some point before the language was first stabilized (2015),
> both were actively pursued.  Here are some musings from the original main
> developer back in 2013ish [1].  Later on, another Mozilla developer also
> talked about a similar topic [2].
> 
> [1]: http://smallcultfollowing.com/babysteps/blog/2013/06/11/on-the-connection-between-memory-management-and-data-race-freedom/
> [2]: https://manishearth.github.io/blog/2015/05/17/the-problem-with-shared-mutability/
> 
> It is interesting that both of them kind of hint at the idea of a large
> single threaded program having similar challenges to a multithreaded
> program, at least when considering how undefined behavior, data
> invalidation, and data races occur.

I understand better now; thanks for these references.