Re: unconstify equivalent for volatile
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-02-18T15:43:50Z
Lists: pgsql-hackers
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes: > I propose to add an equivalent to unconstify() for volatile. When > working on this, I picked the name unvolatize() mostly as a joke, but it > appears it's a real word. Other ideas? Umm ... wouldn't this amount to papering over actual bugs? I can think of legitimate reasons to cast away const, but casting away volatile seems pretty dangerous, and not something to encourage by making it notationally easy. regards, tom lane
Commits
-
Add macro to cast away volatile without allowing changes to underlying type
- 481018f28040 12.0 landed
-
Initialize structure at declaration
- 572e3e6634e5 12.0 landed