Open georgefst opened 2 years ago
Ah, I've just seen this has previously been asked by @sjakobi (no response): https://github.com/quchen/prettyprinter/issues/121#issuecomment-577254902.
Is there any particular reason why
prettyprinter-ansi-terminal
redefines its own versions of these types, isomorphic to the ones upstream?
I speculated about this in https://github.com/quchen/prettyprinter/pull/224#issuecomment-1109810937:
I'm not sure, but I suspect that the local types exist so the internals can be changed with less compatibility hassle. Re-exports also bring their own versioning problems.
Maybe @quchen can comment on the original motivation.
I'm not sure, but I suspect that the local types exist so the internals can be changed with less compatibility hassle. Re-exports also bring their own versioning problems.
I can't really see either of those having much bearing in practice, particularly given how unlikely the ANSI standard is to change any time soon.
Is there any particular reason why
prettyprinter-ansi-terminal
redefines its own versions of these types, isomorphic to the ones upstream? I often find myself needing to resolve conflicting imports due to this, especially since the ones from this package are re-exported throughpretty-simple
.