Snapshot gcc-11-20240111 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20240111/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Happy new year!
This Friday will be the first Sourceware Open Office of 2024.
Join us this Friday, January 12, in #overseers on irc.libera.chat
from 18:00 till 19:00 UTC.
For any questions or ideas about any Sourceware service and/or
integration of cgit, bugzilla, mailinglists, snapshots, mirror
On 1/11/24 12:48, Martin Jambor wrote:
On Wed, Jan 10 2024, Jason Merrill via Gcc wrote:
What formatting style do we want for non-trivial lambdas in GCC sources?
I'm thinking the most consistent choice would be
auto l = [&] (parms) // space between ] (
{ // brace on new
Hi,
On Wed, Jan 10 2024, Jason Merrill via Gcc wrote:
> What formatting style do we want for non-trivial lambdas in GCC sources?
> I'm thinking the most consistent choice would be
>
> auto l = [&] (parms) // space between ] (
>{ // brace on new line, indented two spaces
>
> "Jason" == Jason Merrill via Gcc writes:
Jason> I think we probably want the same formatting for lambdas in function
Jason> argument lists, e.g.
Jason> algorithm ([] (parms)
Jason> {
Jason> return foo;
Jason> });
Jason> Any other opinions?
FWIW gdb did pretty much this same thing
