-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement debugPrint
for built-in file providers
#24156
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is only for print
, right? Not for str
which would be a bigger change.
I'd go for a more Starlark representation, printing those providers as if they were implemented in starlark.
cc @brandjon @tetromino @lberki |
If it doesn't expose non-hermetic / non-deterministic information that we don't want Starlark users to introspect on, then it should be safe for But limiting it to |
66b8bef
to
da35a8b
Compare
That's a good point. I've modified the methods to use I noticed that the providers that derive from |
src/main/java/com/google/devtools/build/lib/analysis/FileProvider.java
Outdated
Show resolved
Hide resolved
src/main/java/com/google/devtools/build/lib/analysis/Runfiles.java
Outdated
Show resolved
Hide resolved
Nice.
My preference would be to print out the Name in all cases (either native or Starlark). I don't know what's current state. |
Simplifies `print` style debugging.
@bazel-io fork 8.1.0 |
(late to the party) Yes, I do have an opinion, which is that this is a good thing :) |
Simplifies `print` style debugging. Closes bazelbuild#24156. PiperOrigin-RevId: 721850583 Change-Id: I8b3c3a1063f1dbfa3c0c1556e1112c1885a5c6a9
Simplifies `print` style debugging. Closes #24156. PiperOrigin-RevId: 721850583 Change-Id: I8b3c3a1063f1dbfa3c0c1556e1112c1885a5c6a9 Commit fe7b4ab Co-authored-by: Fabian Meumertzheim <[email protected]>
Simplifies
print
style debugging.