tree c2dd7f4fa7f90c720fcb73a104dbd8b54ddd1031
parent 1a6a5a1b4a85f61b9b335ba098a7d2e087c64649
author Googler <noreply@google.com> 1574453020 -0800
committer Copybara-Service <copybara-worker@google.com> 1574453082 -0800

bazel syntax: reintroduce element validity check to depset contructor

Also, declare concrete subclasses of analysis.ConfiguredTarget as @Immutable,
and thus Starlark-hashable.

It is possible that user code passes values of other classes that fail
the element validity check. In that case we must either withdraw the check
and phase it in using a flag, or, consider whether the specific value should
be declared immutable/hashable, as was appropriate for ConfiguredTarget.

PiperOrigin-RevId: 282015280