What happened?
With #1052 we are essentially breaking task reexporting with a different name due to how we store task values on the heap. (no longer cloning) therefore this pattern does not work and needs a better api to support it.
Version
Development (host) and target OS/architectures:
Output of bazel --version:
Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file:
Language(s) and/or frameworks involved:
How to reproduce
Any other information?
No response
What happened?
With #1052 we are essentially breaking task reexporting with a different name due to how we store task values on the heap. (no longer cloning) therefore this pattern does not work and needs a better api to support it.
Version
Development (host) and target OS/architectures:
Output of
bazel --version:Version of the Aspect rules, or other relevant rules from your
WORKSPACEorMODULE.bazelfile:Language(s) and/or frameworks involved:
How to reproduce
Any other information?
No response