On Monday, April 22, 2019 3:21:22 PM PDT Eric Anholt wrote:
> Jason Ekstrand writes:
>
> > All,
> >
> > I've seen discussions come up several times lately about whether you should
> > use MAYBE_UNUSED or UNUSED in what scenario and why do we have two of them
> > anyway. That got me thinking a
On Mon, Apr 22, 2019 at 3:11 PM Matt Turner wrote:
>
> On Mon, Apr 22, 2019 at 1:09 PM Kristian Høgsberg wrote:
> >
> > On Mon, Apr 22, 2019 at 12:11 PM Jason Ekstrand
> > wrote:
> > >
> > > All,
> > >
> > > I've seen discussions come up several times lately about whether you
> > > should use
Jason Ekstrand writes:
> All,
>
> I've seen discussions come up several times lately about whether you should
> use MAYBE_UNUSED or UNUSED in what scenario and why do we have two of them
> anyway. That got me thinking a bit. Maybe what we actually want instead
> of MAYBE_UNUSED is something
On Mon, Apr 22, 2019 at 1:09 PM Kristian Høgsberg wrote:
>
> On Mon, Apr 22, 2019 at 12:11 PM Jason Ekstrand wrote:
> >
> > All,
> >
> > I've seen discussions come up several times lately about whether you should
> > use MAYBE_UNUSED or UNUSED in what scenario and why do we have two of them
>
On Mon, Apr 22, 2019 at 12:11 PM Jason Ekstrand wrote:
>
> All,
>
> I've seen discussions come up several times lately about whether you should
> use MAYBE_UNUSED or UNUSED in what scenario and why do we have two of them
> anyway. That got me thinking a bit. Maybe what we actually want
All,
I've seen discussions come up several times lately about whether you should
use MAYBE_UNUSED or UNUSED in what scenario and why do we have two of them
anyway. That got me thinking a bit. Maybe what we actually want instead
of MAYBE_UNUSED is something like this:
#ifdef NDEBUG
#define
