Am Mittwoch, dem 12.07.2023 um 15:23 +0200 schrieb Benjamin Priour via Gcc: > Hi David, > > > Lately I've been working on adding a new state machine to keep track > of > ownership transfers > > and misuses, e.g. to warn about use-after-move, partial or shallow > copy/move. > > I'm trying to stay abstracted from heap allocated regions, and to > rather > work with "resources", > > so that the state machine could be easily further extended. > > However, the whole concern of ownership is really C++-like, and most > of the > checks would require > > things unheard of in vanilla C, such as copy/move operators, ctors & > dtors > ... > > > Using those constructs, it is really doable to guess ownership of > resources, whereas without them it becomes > > much more hazardous. > > So, should we make this new sm -adroitly called sm-ownership- C++- > only ? > > > Doing so would allow the sm to reuse code from under cp/*, thus it'd > reduce > duplicating code and would > > likely lead to less false positives in C++ -more precise function > checks-, > though it would make any future C-support more tedious. > > It's also going against the current flow of porting what's already > done for > C to C++.
A gnu::owner attribute is certainly something which also make sense for C. Martin
