-
-
Notifications
You must be signed in to change notification settings - Fork 95
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
use Base.show #165
use Base.show #165
Conversation
What happens if you remove the entire method? I think the definition might be identical to the one in base... |
I'll have to check once I'm back at my computer in a few days.
… On Jan 19, 2019, at 12:52, Matti Pastell ***@***.***> wrote:
What happens if you remove the entire method? I think the definition might be identical to the one in base...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Tests seem to pass without that method. There's another place where it seems a method is being clobbered:
There the methods don't seem to be identical: the Weave.jl one uses a |
Thanks for the fix and checking! I'll merge now. The overwrite of latex(IO, Markdown.LaTeX) is intentional and it was added to fix #142 . It would be better not to replace base methods and I'll try to fix it at some point. |
There's one place where a
show
method is defined that's notBase.show
. I get errors like thisMy hunch is that somehow the one non-Base show method being defined is somehow blocking the Base ones, but I could be wrong. Changing the function definition to be
Base.show
fixes the error but then I get warnings likeSo maybe this isn't the right approach but I'm proposing it here just in case. @dmbates pointed this out in #149 (even though it didn't address the underlying problem there).