On Thu, 10 Sep 2020, Patrick Palka wrote:
> On Thu, 10 Sep 2020, David Malcolm wrote:
>
> > On Tue, 2020-07-28 at 20:22 -0400, Patrick Palka wrote:
> > > On Tue, 28 Jul 2020, David Malcolm wrote:
> > >
> > > > On Tue, 2020-07-28 at 15:50 -0400, Patrick Palka wrote:
> > > > > Currently the -Wmisl
On Thu, 10 Sep 2020, David Malcolm wrote:
> On Tue, 2020-07-28 at 20:22 -0400, Patrick Palka wrote:
> > On Tue, 28 Jul 2020, David Malcolm wrote:
> >
> > > On Tue, 2020-07-28 at 15:50 -0400, Patrick Palka wrote:
> > > > Currently the -Wmisleading-indentation warning doesn't do any
> > > > analysi
On Tue, 2020-07-28 at 20:22 -0400, Patrick Palka wrote:
> On Tue, 28 Jul 2020, David Malcolm wrote:
>
> > On Tue, 2020-07-28 at 15:50 -0400, Patrick Palka wrote:
> > > Currently the -Wmisleading-indentation warning doesn't do any
> > > analysis
> > > when the guarded statement or the statement aft
On Mon, 10 Aug 2020, Patrick Palka wrote:
> On Tue, 28 Jul 2020, Patrick Palka wrote:
>
> > Currently the -Wmisleading-indentation warning doesn't do any analysis
> > when the guarded statement or the statement after it is produced by a
> > macro, as the mentioned PR illustrates. This means that
On Tue, 28 Jul 2020, Patrick Palka wrote:
> Currently the -Wmisleading-indentation warning doesn't do any analysis
> when the guarded statement or the statement after it is produced by a
> macro, as the mentioned PR illustrates. This means that we warn for:
>
> if (flag)
> foo ();
> ba
On Tue, 28 Jul 2020, David Malcolm wrote:
> On Tue, 2020-07-28 at 15:50 -0400, Patrick Palka wrote:
> > Currently the -Wmisleading-indentation warning doesn't do any
> > analysis
> > when the guarded statement or the statement after it is produced by a
> > macro, as the mentioned PR illustrates.
On Tue, 2020-07-28 at 15:50 -0400, Patrick Palka wrote:
> Currently the -Wmisleading-indentation warning doesn't do any
> analysis
> when the guarded statement or the statement after it is produced by a
> macro, as the mentioned PR illustrates. This means that we warn for:
>
> if (flag)
> f
Currently the -Wmisleading-indentation warning doesn't do any analysis
when the guarded statement or the statement after it is produced by a
macro, as the mentioned PR illustrates. This means that we warn for:
if (flag)
foo ();
bar ();
and yet we don't warn for:
#define BAR bar
if
