| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RfD: more powerful "any" types |
| Date: | 2009-09-09 17:27:57 |
| Message-ID: | E3F77D42-E4EF-4073-904E-6C517663902C@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sep 9, 2009, at 10:17 AM, Tom Lane wrote:
> Well, none, *if* it's defined to have exactly the same runtime
> behavior
> as anyelement does. It sounded like you were arguing for something
> looser. We could certainly define it as being just like anyelement
> but not constrained to match any other argument or result (and, hence,
> not usable as a result type).
Yes, that sounds about right. Is that not basically what Alvaro was
looking for to start with? And is there an "any" array that could work
for variadic functions like sprintf(), as well?
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2009-09-09 17:28:32 | Re: RfD: more powerful "any" types |
| Previous Message | Alvaro Herrera | 2009-09-09 17:24:23 | Re: RfD: more powerful "any" types |