Re: proposal: disallow operator "=>" and use it for named parameters - Mailing list pgsql-hackers

From Tom Lane
Subject Re: proposal: disallow operator "=>" and use it for named parameters
Date
Msg-id 16457.1426002617@sss.pgh.pa.us
Whole thread Raw
In response to Re: proposal: disallow operator "=>" and use it for named parameters  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: proposal: disallow operator "=>" and use it for named parameters  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: proposal: disallow operator "=>" and use it for named parameters  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Thu, Feb 19, 2015 at 3:15 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
>> I am marking this as Ready For Committer, the patch is trivial and works
>> as expected, there is nothing to be added to it IMHO.
>> 
>> The "=>" operator was deprecated for several years so it should not be too
>> controversial either.

> Committed with a few documentation tweaks.

Was there any consideration given to whether ruleutils should start
printing NamedArgExprs with "=>"?  Or do we think that needs to wait?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Denys Rtveliashvili
Date:
Subject: Stateful C-language function with state managed by third-party library
Next
From: Jim Nasby
Date:
Subject: Re: proposal: searching in array function - array_position