tree e101043a0f31ef4baad9005a1740a8bc3850217f
parent fbeb0c9793e146d08c9d6dfdfceaea8b24f86e6c
author gregce <gregce@google.com> 1556204468 -0700
committer Copybara-Service <copybara-worker@google.com> 1556204545 -0700

Remove outdated trimming logic that was harming efficiency.

This arose after observing excessive calls to BuildOptions.trim in https://github.com/bazelbuild/bazel/commit/ab9f2dbc078fc59b1784c2f03da027a75d72b688. This is because ConfigurationResolver.applyTransition was called with "trim fragments mode" on from a *lot* of callers even though this is an outdated interpretation of "trimming" that yields no benefits.

This was originally added in https://github.com/bazelbuild/bazel/commit/b0de919d8657d5809d9ab8315d4665926087d0b4 when the distinction between dynamic configurations and trimmed configurations wasn't yet explicit.

PiperOrigin-RevId: 245235812