Repository navigation
Separate modern CEL runtime configuration, expression compilation, and standard extensions from legacy V1 registries so modern consumers link zero deprecated evaluation code. - #2457
Open
copybara-service[bot] wants to merge 1 commit into
Conversation
copybara-service
Bot
force-pushed
the
test_1021200960
branch
3 times, most recently
from
November 13, 2026 21:46
5e4d8f6 to
85322db
Compare
…d standard extensions from legacy V1 registries so modern consumers link zero deprecated evaluation code. Even after isolating legacy value types, the modern type registry, flat expression builder, shared runtime environment, and standard extension libraries remained coupled to legacy type and function registries. Because builders shared a single environment and extensions registered handlers through legacy adapter wrappers, modern servers linking the standard runtime paid the full code-size cost of the deprecated V1 evaluation stack. Moving legacy registry ownership and lifetime management into dedicated wrappers reserved for legacy expression builders lets the modern runtime environment operate standalone without touching legacy symbols. Splitting the extension registrars and protobuf visibility boundaries similarly allows modern callers to initialize standard extension functions directly against the modern function registry while keeping legacy wrapper headers intact for remaining V1 callers. PiperOrigin-RevId: 1021200960
copybara-service
Bot
force-pushed
the
test_1021200960
branch
from
November 13, 2026 21:49
85322db to
8ee3f36
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
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.
Separate modern CEL runtime configuration, expression compilation, and standard extensions from legacy V1 registries so modern consumers link zero deprecated evaluation code.
Even after isolating legacy value types, the modern type registry, flat expression builder, shared runtime environment, and standard extension libraries remained coupled to legacy type and function registries. Because builders shared a single environment and extensions registered handlers through legacy adapter wrappers, modern servers linking the standard runtime paid the full code-size cost of the deprecated V1 evaluation stack.
Moving legacy registry ownership and lifetime management into dedicated wrappers reserved for legacy expression builders lets the modern runtime environment operate standalone without touching legacy symbols. Splitting the extension registrars and protobuf visibility boundaries similarly allows modern callers to initialize standard extension functions directly against the modern function registry while keeping legacy wrapper headers intact for remaining V1 callers.