-
Notifications
You must be signed in to change notification settings - Fork 36
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
prettyprinter has very long module names #110
Comments
I still like this idea. @quchen, what do you think? |
I totally agree the module names are too long. This was brought up to me shortly after the initial release of the library already, but I did not think it was a good time to do something about it. If there is a non-breaking way to go about this, go ahead! I would hate to have maintainers to have to hack around this using lots of |
This removes -Werror from CI, since the import of Prettyprinter.Render.Tutorials.StackMachineTutorial results in a deprecation warning that turned out to be very tricky to disable. Context: #110.
This is the deprecation plan that I have included in the changelog for v1.7.0 and the associated releases for
|
@istathar has a nice recommendation for de-cluttering the module overview, that we should consider using when we properly deprecate the old module hierarchy.
|
Resolved in #203 |
I remember being frustrated by the long module names when working on
dhall
, especially when I had to reformat qualified imports after adding an import likeThe basic idea would be to replace the
Data.Text.Prettyprint.Doc
prefix with justPrettyprinter
.The change would probably happen in multiple phases:
Prettyprinter
modules, but re-export everything from the old modules.Thoughts?
The text was updated successfully, but these errors were encountered: