Re: Don't cast away const where possible - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Don't cast away const where possible
Date
Msg-id b660d0d6-e04d-4bf9-af1a-96b721be657f@eisentraut.org
Whole thread Raw
In response to Don't cast away const where possible  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
List pgsql-hackers
On 18.12.25 14:55, Bertrand Drouvot wrote:
> Some functions are casting away the const qualifiers from their signatures in
> local variables.

@@ -1304,8 +1304,8 @@ merge_overlapping_ranges(FmgrInfo *cmp, Oid colloid,
  static int
  compare_distances(const void *a, const void *b)
  {
-       DistanceValue *da = (DistanceValue *) a;
-       DistanceValue *db = (DistanceValue *) b;
+       const DistanceValue *da = (const DistanceValue *) a;
+       const DistanceValue *db = (const DistanceValue *) b;

I wonder if the better fix here wouldn't be to get rid of the cast. 
It's not necessary, and without it the compiler would automatically warn 
about qualifier mismatches.  These comparison functions seem to be a 
common pattern.




pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Improve logical replication usability when tables lack primary keys
Next
From: VASUKI M
Date:
Subject: Re: [PATCH] psql: tab completion for ALTER ROLE ... IN DATABASE ...