Re: Improve readability by using designated initializers when possible

Поиск
Список
Период
Сортировка
От Jelte Fennema-Nio
Тема Re: Improve readability by using designated initializers when possible
Дата
Msg-id CAGECzQQjQSJ3-bahHv8p7R3SCxyw=g7M0=+CJN5FmktC7hJZog@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Improve readability by using designated initializers when possible  (Japin Li <japinli@hotmail.com>)
Ответы Re: Improve readability by using designated initializers when possible  (Japin Li <japinli@hotmail.com>)
Список pgsql-hackers
Дерево обсуждения 
On Tue, 5 Mar 2024 at 15:30, Japin Li <japinli@hotmail.com> wrote:
> There is a warning if remove it, so I keep it.
>
> /home/japin/Codes/postgres/build/../src/backend/executor/execExprInterp.c:118:33: warning: label ‘CASE_EEOP_LAST’
definedbut not used [-Wunused-label] 
>   118 | #define EEO_CASE(name)          CASE_##name:
>       |                                 ^~~~~
> /home/japin/Codes/postgres/build/../src/backend/executor/execExprInterp.c:1845:17: note: in expansion of macro
‘EEO_CASE’
>  1845 |                 EEO_CASE(EEOP_LAST)
>       |                 ^~~~~~~~

I think if you remove the EEO_CASE(EEOP_LAST) block the warning should
go away. That block is clearly marked as unreachable, so it doesn't
really serve a purpose.

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Dump-restore loosing 'attnotnull' bit for DEFERRABLE PRIMARY KEY column(s).
Следующее
От: Jeff Davis
Дата:
Сообщение: Re: pgsql: Fix search_path to a safe value during maintenance operations.