Andrew Dunstan <andrew@dunslane.net> writes:
> Just a thought - if we are messing with the List definition should we at
> the same time address the strict aliasing issues arising from Node's
> multiple personalities (I think it is the main offender).
> Or is the intention never to do this, or not any time soon?
I have no intention of messing with the Node concept; it's built into
the backend far too firmly to consider any significant change.
I don't think we understand exactly what we'd have to avoid in order to
enable strict aliasing, but if it requires getting rid of Node then it
ain't happening. (I doubt that it does, anyway. I think the issues are
probably quite localized. The main problem I see is that we don't have
any trustworthy check to find out everyplace that strict aliasing could
cause problems.)
regards, tom lane