Hi,

Last year, Anton raised the conflict on his patch "lavfi: get rid of 
FF_INTERNAL_FIELDS", 
https://lists.ffmpeg.org//pipermail/ffmpeg-devel/2023-January/306102.html, to 
the TC to decide on.

At the time, the TC did not come to any conclusion on the matter. Recently, 
Anton raised the question again, and this time, the current TC managed to 
successfully discuss the matter and come to a conclusion.

The main arguments raised were about API consistency, prevention of accidental 
inclusions, as well as explicitness in marking a field as public or private. 
These advantages were deemed to be worth the trade-off of making access to 
private fields slightly less convenient.

The TC has voted on the matter, with 4 votes in favour of the patch, 1 vote 
preferring to look for other solutions, and Anton himself abstaining from the 
vote.

Therefore, the matter has been decided, approving the patch at hand.

Regards,
The FFmpeg Technical Committee
- Jan Ekström
- Mark Thompson
- Martin Storsjö
- Michael Niedermayer
- Niklas Haas
- Anton Khirnov

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".

Reply via email to