Second edition of the Carbon Copy is out! github.com/carbon-language/c… More details over on Hachyderm: hachyderm.io/@chandlerc/1122…

Chandler Carruth (@chandlerc@hachyderm.io)

Second edition of the Carbon Copy is out! https://github.com/carbon-language/carbon-lang/discussions/3869 This one discusses Carbon's "unformed state" as a way to address safety risks of uninitiali...

hachyderm.io
1
7
31
I like "unformed" here -- seems close to minimum requirements of "partially formed". I don't see rationale for requiring support for multiple destructions, though. Won't that often require users branching in destructors when not vacuous? Is rationale for that aspect up anywhere?
2
1
Replying to @CppSage
The specific goal is to represent the large body of types which have a viable idempotent state for destructors. As for how multiple destruction comes up, some of it may be in the proposal. My memory is that it is only about reducing cost -- specifically dynamic tracking.

Apr 9, 2024 · 1:47 AM UTC