Re: embedded list v3
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org, Alvaro Herrera <alvherre@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, Peter Geoghegan <peter@2ndquadrant.com>
Date: 2012-09-30T16:57:32Z
Lists: pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes: > Patch 0001 contains a assert_compatible_types(a, b) and a > assert_compatible_types_bool(a, b) macro which I found very useful to make it > harder to misuse the api. I think its generally useful and possibly should be > used in more places. This seems like basically a good idea, but the macro names are very unfortunately chosen: they don't comport with our other names for assertion macros, and they imply that the test is symmetric which it isn't. It's also unclear what the point of the _bool version is (namely, to be used in expression contexts in macros). I suggest instead AssertVariableIsOfType(varname, typename) AssertVariableIsOfTypeMacro(varname, typename) Or possibly we should leave off the "Assert" prefix, since this will be a compile-time-constant check and thus not really all that much like the existing run-time Assert mechanism. Or write "Check" instead of "Assert", or some other verb. Anybody got another color for this bikeshed? regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Provide some static-assertion functionality on all compilers.
- 0d0aa5d29175 9.3.0 cited
-
Add infrastructure for compile-time assertions about variable types.
- ea473fb2dee7 9.3.0 cited
-
Remove 576 references of include files that were not needed.
- e0522505bd13 8.2.0 cited
-
More include file adjustments.
- b43ebe5f83b2 8.2.0 cited
-
Allow each C include file to compile on its own by including any needed
- b85a965f5fc7 8.2.0 cited