Kacper Michajlow:
> On Thu, 3 Apr 2025 at 11:39, Martin Storsjö wrote:
>>
>> On Thu, 3 Apr 2025, Kacper Michajlow wrote:
>>
>>> Hello,
>>>
>>> It would be nice to have configure time ability to disable all
>>> `FF_API_*` for testing purposes.
>>>
>>> As we know not all code can be marked to emit W
Hi
On Thu, Apr 03, 2025 at 11:02:01AM +0200, Kacper Michajlow wrote:
> Hello,
>
> It would be nice to have configure time ability to disable all
> `FF_API_*` for testing purposes.
>
> As we know not all code can be marked to emit Wdeprecated.
> Specifically #defines doesn't emit any warning and
On Thu, 3 Apr 2025 at 11:39, Martin Storsjö wrote:
>
> On Thu, 3 Apr 2025, Kacper Michajlow wrote:
>
> > Hello,
> >
> > It would be nice to have configure time ability to disable all
> > `FF_API_*` for testing purposes.
> >
> > As we know not all code can be marked to emit Wdeprecated.
> > Specifi
On Thu, 3 Apr 2025, Kacper Michajlow wrote:
Hello,
It would be nice to have configure time ability to disable all
`FF_API_*` for testing purposes.
As we know not all code can be marked to emit Wdeprecated.
Specifically #defines doesn't emit any warning and it's easy to miss
such depreciation b
Hello,
It would be nice to have configure time ability to disable all
`FF_API_*` for testing purposes.
As we know not all code can be marked to emit Wdeprecated.
Specifically #defines doesn't emit any warning and it's easy to miss
such depreciation before it's actually removed.
The breakage of c
