Re: Add new for_each macros for iterating over a List that do not require ListCell pointer
От | Jelte Fennema-Nio |
---|---|
Тема | Re: Add new for_each macros for iterating over a List that do not require ListCell pointer |
Дата | |
Msg-id | CAGECzQT_BUONYWLrUfuAC0rQcWiSddzv9EN+VvihNqnoVrtMKQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Add new for_each macros for iterating over a List that do not require ListCell pointer (Nathan Bossart <nathandbossart@gmail.com>) |
Ответы |
Re: Add new for_each macros for iterating over a List that do not require ListCell pointer
Re: Add new for_each macros for iterating over a List that do not require ListCell pointer |
Список | pgsql-hackers |
On Wed, 3 Jan 2024 at 20:55, Nathan Bossart <nathandbossart@gmail.com> wrote: > > I spent some time preparing this for commit, which only amounted to some > light edits. I am posting a new version of the patch in order to get one > more round of cfbot coverage and to make sure there is no remaining > feedback. Overall your light edits look good to me. The commit message is very descriptive and I like the shortening of the comments. The only thing I feel is that I think lost some my original intent is this sentence: + * different types. The outer loop only does a single iteration, so we expect + * optimizing compilers will unroll it, thereby optimizing it away. The "we expect" reads to me as if we're not very sure that compilers do this optimization. Even though we are quite sure. Maybe some small changes like this to clarify that. The outer loop only does a single iteration, so we expect that **any** optimizing compilers will unroll it, thereby optimizing it away. **We know for sure that gcc and clang do this optimization.**
В списке pgsql-hackers по дате отправления: