You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 through pretty-simple.
The text was updated successfully, but these errors were encountered:
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
.The text was updated successfully, but these errors were encountered: