We've moved to using bazel modules and haven't kept the WORKSPACE style deps up to date, so compiling with
--noenable_bzlmod or older versions (<7) of bazel no longer work.

PiperOrigin-RevId: 835287560

BytesValue::WrapUnsafe and StringValue::WrapUnsafe do not attempt to validate ownership, but avoid copying the underlying string data as much as possible.
PiperOrigin-RevId: 836237389

This overload is never used outside of tests after refactors.

PiperOrigin-RevId: 839472867

…ying.

`auto var = FunctionReturningConstRef();` causes a copy while `const auto& var = FunctionReturningConstRef();` does not cause any copies. Example: https://godbolt.org/z/37hETqc3q

PiperOrigin-RevId: 839669874

PiperOrigin-RevId: 839841283

Update the optimizer to permit invalid constant map keys (by not rewriting the select chain when encountered). These should not be allowed per spec, but the CEL implementations generally permit it to tolerate `dyn` keys.

PiperOrigin-RevId: 839852761

…ction and copy of `SourceInfo`.

`const auto& var = ptr == nullptr ? ProtoMessage() : *ptr;` can call `ProtoMessage::ProtoMessage` constructor whenever `ptr` is null. But, due to how ternary operators behave compiler will copy `*ptr` even when `ptr` is not null.

OTOH, `const auto& var = ptr == nullptr ? ProtoMessage::default_instance() : *ptr;` won't do the similar call because `ProtoMessage::default_instance()` already returns a const reference.

- The subtle difference between ternary operator and if-else can be seen here: https://godbolt.org/z/bPvjjn6dP
- The overall change is similar to this: https://godbolt.org/z/8Phd9nzEh

PiperOrigin-RevId: 840528597

PiperOrigin-RevId: 840798139

PiperOrigin-RevId: 840888710