Re: Are we missing (void) when return value of fsm_set_and_search is ignored? - Mailing list pgsql-hackers

From Bharath Rupireddy
Subject Re: Are we missing (void) when return value of fsm_set_and_search is ignored?
Date
Msg-id CALj2ACWn8WNtvuOOuJD95fe1G+pSHfX+Fi8Sa_ai=QZoBEoOgA@mail.gmail.com
Whole thread Raw
In response to Re: Are we missing (void) when return value of fsm_set_and_search is ignored?  (Julien Rouhaud <rjuju123@gmail.com>)
List pgsql-hackers
On Thu, Jun 3, 2021 at 5:22 PM Julien Rouhaud <rjuju123@gmail.com> wrote:
>
> On Thu, Jun 3, 2021 at 6:54 PM Bharath Rupireddy
> <bharath.rupireddyforpostgres@gmail.com> wrote:
> >
> > It looks like for some of the fsm_set_and_search calls whose return
> > value is ignored (in fsm_search and RecordPageWithFreeSpace), there's
> > no (void). Is it intentional? In the code base, we generally have
> > (void) when non-void return value of a function is ignored.
>
> That's a good practice, +1 for changing that.

Thanks. PSA v1 patch.

With Regards,
Bharath Rupireddy.

Attachment

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: Duplicate history file?
Next
From: Peter Eisentraut
Date:
Subject: Re: Are we missing (void) when return value of fsm_set_and_search is ignored?