-
Notifications
You must be signed in to change notification settings - Fork 13.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
8ec3942
commit e2d7df5
Showing
2 changed files
with
96 additions
and
96 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
e2d7df5
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.
I'd like to ask about the reasoning behind making all the
print_*
methods private. I use libsyntax in my project to build an AST, then print it to a file with comments added and after updating libsyntax, there no longer seems to be a way to do this. C2Rust has a similar issue - they solved it by copying thelibsyntax/print
module into their project as a subcrate which doesn't seem very maintainable long term. In the end i started using their fork in my project too. I feel like this somewhat defeats the purpose of having some functionality of rustc as independent crates which other tools can use instead of writing their own buggy implementations.