Would you be interested in an **early** preview of the design we're converging on for Carbon's memory safety model?
If so, Josh on the Carbon team is planning to give a 2 hour talk covering:
- What the design is
- How it prevents use after free and data races
- What expressivity we expect it to support
- How it will support a transition from C++
It will only lightly cover comparisons with Rust's memory safety approach.
Again, this is an early preview, before we have started on implementation or even a more polished end-to-end write-up. Some of the design may change, and there are still some open questions, but the core looks reasonably solid and very promising.
What we are hoping to achieve with the presentation:
- Get folks up to speed on what we are thinking.
- Getting feedback earlier in our process while making changes is easier.
- Help us refine our exposition.
This talk will not go into:
- How we arrived at this design
- Concerns we had with alternatives we considered
- How the design will be implemented
We are totally okay if you would rather wait until we are further along -- we hope to give regular updates to the community. Also, while this session won't be recorded, we do plan to record the presentation in case you'd prefer to consume a video instead of attending live. And last but not least, our next step is a reasonably polished and complete written design if you would prefer to read a document.
We also expect detailed feedback on our approach and how we are describing the approach would mostly be asynchronous after you've had some time to digest the talk. We only expect to have time for minimal initial reactions and clarifying questions given the depth and complexity of the subject. Our plan is to follow-up afterward in email and/or a document to collect this feedback.
If you're interested in attending live, please put when would work for you here: https://www.when2meet.com/?36904183-wO2j2 and DM me or reach out on our Discord server: https://discord.com/channels/655572317891461132/708431848715452476
We'll post an update with the time(s) selectad and the join link (we use Google Meet for better or worse) to that Discord channel.