Skip to content
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

DOC: Fix the manual for method ambiguities #17112

Closed
wants to merge 1 commit into from

Conversation

iglpdc
Copy link
Contributor

@iglpdc iglpdc commented Jun 25, 2016

The way of handling method ambiguities changed in #16125. Now Julia throws
an error when calling an ambiguous methods, instead of just
giving a warning when it was defined. This updates the manual to reflect
the change.

Fixes #16630.

The way of handling method ambiguities changed in JuliaLang#16125. Now Julia throws
an error when calling an ambiguous methods, instead of just
giving a warning when it was defined. This updates the manual to reflect
the change.

Fixes JuliaLang#16630.
@iglpdc
Copy link
Contributor Author

iglpdc commented Jun 25, 2016

I understand that the order in which one defines the methods doesn't matter anymore (before #16125 g(x::Float64, y::Float64) = 2x + 2y; had to be defined before the other two), so I removed the text regarding that.

@iglpdc
Copy link
Contributor Author

iglpdc commented Jun 25, 2016

@omus I think we were doing this at the same time.... I'm closing this.

@iglpdc iglpdc closed this Jun 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant