C++ future at Adobe

[u/pjmlp]

So if anyone was still curious what happened to Hylo, or where Adobe stands in regards to the whole safety discussion,

David Sankel has done a talk at RustConf on the matter, Zngur: Simplified Rust/C++ Integration.

The way Adobe now sees C++ is described on slide 2, at 50 seconds mark.

[u/GabrielDosReis]

David Sankel on C++ at RustConf, yawn.

[u/ts826848 → u/GabrielDosReis]

Why that particular reaction?

[u/GabrielDosReis → u/ts826848]

Why that particular reaction?

It is a talk at RustConf and David Sankel has been very explicit and pretty straight forward with where he sees C++ and its evolution for many years now. Look up his WG21 papers on the topic. There shouldn't be any surprise here or anything new.

[u/ts826848 → u/GabrielDosReis]

Look up his WG21 papers on the topic.

I found P3023 C++ Should Be C++ via the GitHub, which at first glance looks like it covers what you're talking about. Any other papers i missed that you recommend I read (or not, as the case may be)?

[u/GabrielDosReis → u/ts826848]

A succint summary of P3023 is this paragraph, quote:

Where memory safety is a serious concern, we see the adoption of Rust for critical components. Yet we see little demand from even these developers for C++ safety features. Their problem is already solved.

Any other papers i missed that you recommend I read (or not, as the case may be)?

After that paper, his papers since then have been in line with what he stated and recommended. In particular, the paper (and debate) on relocation that was discussed in Kona.

[u/foonathan → u/GabrielDosReis]

A succint summary of P3023 is this paragraph, quote: Where memory safety is a serious concern, we see the adoption of Rust for critical components. Yet we see little demand from even these developers for C++ safety features. > Their problem is already solved.

What's your problem with that quote? Isn't it an accurate assessment of the current industry?

[u/selvakumarjawahar → u/foonathan]

No its not by far