4 ms·
No, his lifetime work, e.g. https://herbsutter.com/2018/09/20/lifetime-profile-v1-0-posted/ https://herbsutter.com/2018/09/20/lifetime-profile-v1-0-post...
by sendfoods 4y ago
No, his lifetime work, e.g. https://herbsutter.com/2018/09/20/lifetime-profile-v1-0-posted/ https://herbsutter.com/2018/09/20/lifetime-profile-v1-0-post...
- pjmlp 4y agoNo that was a proof of concept for a paper that went nowhere. VC++ analysis builds up on SAL infrastructure. https://learn.microsoft.com/en-us/cpp/code-quality/understanding-sal?view=msvc-170 https://learn.microsoft.com/en-us/cpp/code-quality/understan... "Closing the Gap between Rust and C++ Using Principles of Static Analysis - CppCon 2020" https://www.youtube.com/watch?v=_pQGRr4P16w https://www.youtube.com/watch?v=_pQGRr4P16w There is also a clang work on lifetimes, but little progress has happened since 2019. "Lifetime analysis for everyone - CppCon 2019" https://www.youtube.com/watch?v=d67kfSnhbpA https://www.youtube.com/watch?v=d67kfSnhbpA
- sendfoods 4y agoSAL, as I understand it, is Visual Studio/Microsoft only? Do you have any idea if this work will make it to clang/gcc/g++?
- int_19h 4y agoSAL is deliberately designed such that it can be defined as a bunch of macros that expand to whatever compiler-specific magic the implementation needs (e.g. MSYS64 doesn't support it at all, but they define all those macros as no-op, so code still compiles). So in principle it could work across implementations.