Make want_legacy_size_classes a no-op. - #601
Merged
Merged
Conversation
copybara-service
Bot
force-pushed
the
test_973775279
branch
5 times, most recently
from
August 31, 2026 16:46
3787d3e to
21544dd
Compare
Now that we have 24 and 48 in the normal size classes, there should be little need left for the legacy size classes (and since there are so many of them, they bloat the metadata). Make the flag a no-op, so that we can remove it in a while if nothing goes wrong. PiperOrigin-RevId: 973965375
copybara-service
Bot
force-pushed
the
test_973775279
branch
from
August 31, 2026 17:46
21544dd to
a4aa9e3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make want_legacy_size_classes a no-op.
Now that we have 24 and 48 in the normal size classes,
there should be little need left for the legacy size classes
(and since there are so many of them, they bloat the metadata).
Make the flag a no-op, so that we can remove it in a while
if nothing goes wrong.