On Wednesday, January 10th, 2024 at 7:34 PM, Jason Merrill via Gcc
wrote:
>
>
> On 1/10/24 16:41, Marek Polacek wrote:
>
> > On Wed, Jan 10, 2024 at 04:24:42PM -0500, Jason Merrill wrote:
> >
> > > On 1/10/24 15:59, Marek Polacek wrote:
> > >
> > > > On Wed, Jan 10, 2024 at 02:58:03P
On 1/10/24 16:41, Marek Polacek wrote:
On Wed, Jan 10, 2024 at 04:24:42PM -0500, Jason Merrill wrote:
On 1/10/24 15:59, Marek Polacek wrote:
On Wed, Jan 10, 2024 at 02:58:03PM -0500, Jason Merrill via Gcc wrote:
What formatting style do we want for non-trivial lambdas in GCC sources?
I'm think
Hi Arpit!
First, welcome to GCC, and I appreciate your enthousiasm!
On 2023-12-30T22:30:37+0530, CS21B062 ARPIT GUPTA wrote:
> Dear GCC Community,
>
> I hope this email finds you well. My name is Arpit and I am writing to
> express my interest in participating in GSoC, specifically for the
> Rus
On Wed, Jan 10, 2024 at 04:24:42PM -0500, Jason Merrill wrote:
> On 1/10/24 15:59, Marek Polacek wrote:
> > On Wed, Jan 10, 2024 at 02:58:03PM -0500, Jason Merrill via Gcc wrote:
> > > What formatting style do we want for non-trivial lambdas in GCC sources?
> > > I'm thinking the most consistent ch
On 1/10/24 15:59, Marek Polacek wrote:
On Wed, Jan 10, 2024 at 02:58:03PM -0500, 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 ] (
{
In the words of Nick Danger: "You just saved me a lot of investigative
work."
Thank you so much.
Bob D.
-Original Message-
From: Jakub Jelinek
Sent: Wednesday, January 10, 2024 15:51
To: Robert Dubner
Cc: 'GCC Mailing List'
Subject: Re: I am causing valgrind errors...
On Wed, Jan 10
On Wed, Jan 10, 2024 at 02:58:03PM -0500, 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 t
On Wed, Jan 10, 2024 at 02:47:08PM -0600, Robert Dubner wrote:
> Here's the thing: when I run valgrind on the compilation -- not on the
> executable, but on the compiler with the COBOL front end -- I am getting a
> bunch of errors that look like variations of this:
>
> ==1232157== Command: /hom
This message is a bit of a Hail Mary play. I am not asking anybody to spend
any real effort on this question; I am, instead, hoping that somebody will
say, "Oh, sure; you can fix that by doing so-and-so..." or "That happens
when the GENERIC tree is ..."
Jim Lowden and I are working on a COBOL
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
return stuff;
};
By default, recent emacs lines up the { with
> Date: Tue, 9 Jan 2024 21:02:44 +0100
> Cc: i...@google.com, gcc-patc...@gcc.gnu.org, gcc@gcc.gnu.org
> From: Björn Schäpers
>
> Am 07.01.2024 um 18:03 schrieb Eli Zaretskii:
> > In that case, you an call either GetModuleHandeExA or
> > GetModuleHandeExW, the difference is minor.
>
> Here an up
11 matches
Mail list logo
