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 sta
Hi,
On 13/07/2023 10:48, David Malcolm wrote:
(apologies for top-posting; I'm on vacation and don't have my usual email setup)
Sounds interesting, but I'm having difficulty imagining exactly what
you have in mind.
Can you post one or more concrete examples of buggy code that would be
caught by s
(apologies for top-posting; I'm on vacation and don't have my usual email setup)
Sounds interesting, but I'm having difficulty imagining exactly what
you have in mind.
Can you post one or more concrete examples of buggy code that would be
caught by such a warning?
Why wouldn't it be caught by C+
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
