On Thu, Jun 3, 2021 at 6:54 PM Bharath Rupireddy <bharath.rupireddyforpostg...@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.
