C++ is stealing some ideas from Rust...
Conversation
Notices
-
Embed this notice
cuddle (cuddle@mastodon.bsd.cafe)'s status on Wednesday, 27-Dec-2023 22:51:41 JST cuddle -
Embed this notice
gnutelephony (gnutelephony@floss.social)'s status on Wednesday, 27-Dec-2023 22:51:39 JST gnutelephony @cuddle I now have a sync pointer template wrapper that hides an object or container as a private member and uses a locked accessor pointer, so there is always a lock (exclusive or rw) asserts when accessing the shared object, which basically was stolen out of how locking works in rust.
-
Embed this notice
gnutelephony (gnutelephony@floss.social)'s status on Wednesday, 27-Dec-2023 23:12:34 JST gnutelephony @cuddle code can live a long time, often much longer than expected, decades even.
-
Embed this notice
cuddle (cuddle@mastodon.bsd.cafe)'s status on Wednesday, 27-Dec-2023 23:12:35 JST cuddle @gnutelephony That sounds great on hands. But honestly, I found it hilarious that the ISO C++ community now needs to steal ideas from others. I'm kind of disappointed.
Also considering the amount of C++ code, I'm not sure if the entire community can move or take advantage of newer C++ features in a decade or so. Many people love backward compatibility, including me. Features need to be included on the compiler side as well.
-
Embed this notice