-
Notifications
You must be signed in to change notification settings - Fork 26
Namespace collision #10
Comments
Yup. I don't think that's going to change. On Saturday, June 18, 2016, Josh Day [email protected] wrote:
|
I commonly see/use |
For clarity, I ran into this doing something like type A
mat::Matrix{Float64}
end
@recipe function f(a::A)
n, d = size(a.mat)
...
end |
I could see changing it to 'kw', which shouldn't clash as much. The problem On Saturday, June 18, 2016, Josh Day [email protected] wrote:
|
That's a fair reason for wanting to keep it as is, but it's a strange gotcha. Is there a way to get a more informative error? |
I suppose i could search for 'd' on the lhs of an equals and warn. And I do see that 'kw' might be better than 'd'. It's just gonna cause a On Saturday, June 18, 2016, Josh Day [email protected] wrote:
|
The whole point of having |
'-->' and ':=' notation is certainly to reduce the need to refer to 'd' On Saturday, June 18, 2016, Diego Javier Zea [email protected]
|
If you want to change from Step 1) emit deprecations warnings if |
@jw3126 I'd support this if you'd make a coordinated set of PR's implementing this to 1) all repos in JuliaPlots, and 2) all packages depending on RecipesBase that have used |
@mkborregaard Wow. How does one find the packages depending on a given package? If you have a list of packages depending on Plots/RecipiesBase I can at least do a bit of grepping and see if these PRs are possible with sane amount of work. |
👍 |
|
This is all files that contain |
Since Step 1) emit deprecations warnings if Any thoughts? |
Hey, thanks this is great. One thought - with regards the potential for conflicts, I believe they may in fact be even bigger with |
fixed by #29 |
I apparently can't use a variable with the name
d
The text was updated successfully, but these errors were encountered: