Received-SPF: pass (google.com: domain of linux-kernel+bounces-23595-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Date: Thu, 11 Jan 2024 12:39:33 +0000
From: Chris Down <chris@chrisdown.name>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	David Howells <dhowells@redhat.com>, linux-kernel@vger.kernel.org,
	pinskia@gmail.com
Subject: Re: [PATCH 00/45] C++: Convert the kernel to C++
Message-ID: <ZZ_hhT6N9tqKuB2c@chrisdown.name>
References: <152261521484.30503.16131389653845029164.stgit@warthog.procyon.org.uk>
 <3465e0c6-f5b2-4c42-95eb-29361481f805@zytor.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <3465e0c6-f5b2-4c42-95eb-29361481f805@zytor.com>
User-Agent: Mutt/2.2.12 (2023-09-09)

H. Peter Anvin writes:
>We already *do* use constructors and *especially* destructors for a 
>lot of objects, we just call them out.
>
>Note that modern C++ also has the ability to construct and destruct 
>objects in-place, so allocation and construction/destruction aren't 
>necessarily related.
>
>There is no reason you can't do static initialization where possible; 
>even constructors can be evaluated at compile time if they are 
>constexpr.

Side note for the constructor and destructor discussion: should we be more 
widely marketing the __cleanup() infrastructure that Peter added a year or so 
ago? It likely helps a lot with at least some of these cases. In systemd we use 
__attribute__((cleanup)) pretty widely and my experience is that it's made the 
code a lot easier to both create and consume.