Skip to content

Conversation

@cary-ilm
Copy link
Member

@cary-ilm cary-ilm commented Sep 8, 2025

The methods are deprecated for use in application code, but no reason to pollute the build with warnings about the remaining internal usage.

Also, InputPart::isOptimizationEnabled() presumably should be marked as deprecated, since all it does is call the deprecated InputFile::isOptimizationEnabled()

…attributes

The methods are deprecated for use in application code, but no reason
to pollute the build with warnings about the remaining internal usage.

Signed-off-by: Cary Phillips <cary@ilm.com>
@cary-ilm
Copy link
Member Author

cary-ilm commented Oct 5, 2025

@peterhillman, could you take a look at this?

@peterhillman
Copy link
Contributor

We should be able to remove testOptimized completely. @kdt3rd is testOptimizedInterleavePatterns also unnecessary now? That was originally there to test functionality of code that is now removed, but is it worth keeping it as a test that verifies that the library correctly unpacks into various arrangements of interleaved frame buffers?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants