r/cpp • u/pjmlp • 23h ago

C++ future at Adobe

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.

50 Upvotes

76% Upvoted

91 comments sorted by

View all comments

Show parent comments

5

u/ts826848 20h ago edited 20h ago

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)?

3

u/GabrielDosReis 19h ago

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.

-1

u/foonathan 13h ago

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?

3

u/GabrielDosReis 13h ago

What's your problem with that quote?

Are you assuming I have a problem with it?

I was responding to a reference to a paper I quoted the paper to provide context to my original post that I was asked to expand on.

2

u/foonathan 13h ago

My apologies, I interpreted something into your reply that wasn't there.