digitalmars.D - Article on where C++ is heading with memory management
- Ola Fosheim =?UTF-8?B?R3LDuHN0YWQ=?= (11/11) Sep 23 2015 https://github.com/isocpp/CppCoreGuidelines/raw/master/docs/Lifetimes%20...
- cym13 (4/15) Sep 23 2015 I'd add a "Profile" step but this article is indeed interesting,
- Ola Fosheim =?UTF-8?B?R3LDuHN0YWQ=?= (4/5) Sep 24 2015 Video from the presentation at CppCon:
https://github.com/isocpp/CppCoreGuidelines/raw/master/docs/Lifetimes%20I%20and%20II%20-%20v0.9.1.pdf A worthwhile read for those interested in where C++ is heading with regards to static analysis etc. External analyzers might be an interesting direction for a gc-free D as it might be less intrusive than what Rust is doing. E.g.: 1. Develop using the manual annotations, but use the GC to prevent memory issues during initial coding. 2. Run checker and fix the code. Turn off GC. 3. Run in debugger, fix code, go to 2. ?
Sep 23 2015
On Wednesday, 23 September 2015 at 11:52:53 UTC, Ola Fosheim Grøstad wrote:https://github.com/isocpp/CppCoreGuidelines/raw/master/docs/Lifetimes%20I%20and%20II%20-%20v0.9.1.pdf A worthwhile read for those interested in where C++ is heading with regards to static analysis etc. External analyzers might be an interesting direction for a gc-free D as it might be less intrusive than what Rust is doing. E.g.: 1. Develop using the manual annotations, but use the GC to prevent memory issues during initial coding. 2. Run checker and fix the code. Turn off GC. 3. Run in debugger, fix code, go to 2. ?I'd add a "Profile" step but this article is indeed interesting, thanks :-)
Sep 23 2015
On Wednesday, 23 September 2015 at 11:52:53 UTC, Ola Fosheim Grøstad wrote:https://github.com/isocpp/CppCoreGuidelines/raw/master/docs/Lifetimes%20I%20and%20II%20-%20v0.9.1.pdfVideo from the presentation at CppCon: https://youtu.be/hEx5DNLWGgA
Sep 24 2015