https://github.com/JuliaLang/julia/pull/22834 Just a heads up. In my estimation, this could very well be the single biggest source of deprecation warnings ever, and that’s saying something. If anyone has any final thoughts, now is the time.

Would it be possible to extract that functionality into a standalone script to fix up Julia source files?

Just to be clear, this is “about to drop” in 0.7-master, not a 0.6 feature?

Yes. We could also make a GitHub bot or integration of some sort.

As Jeff said, yes, on 0.7-DEV – there will be no new features or breaking changes on 0.6.

yup, https://gist.github.com/ZacLN/2f0d66c651647e32eae85e58102315cb fixdep(filename, overwrite = false) EDIT: though without the full namespace scoping it can’t distinguish between function calls and type constructors

I’m not convinced of this idea myself, but I thought I’d throw it out there. To ease this exceptional deprecatastrophe, perhaps it would make sense to have a special 0.6.1 release halfway through the 0.6 life-cycle in which the only change is this deprecation. This might make the transition easier on people since it won’t be accompanied by lots of other deprecations and errors. The alternative thinking is that it is better to resolve deprecations all at once, but in practice I’ve noticed that it sometimes takes them a long time to get fixed, so perhaps a staged approach is better.

I think that 0.7 is largely serving that purpose by providing a smoother deprecation path to 1.0.

I don’t think that making people update deprecations more times is helpful. It’s not all that hard to do, it’s just kind of annoying, so doing it fewer times is generally better.

Here is a bit of an extension to the fixer by @ZacLN. It patches all the julia files in a package on a checked out branch, and makes a commit with the changes. Blam, ready for PR. I just did https://github.com/JuliaStats/Distances.jl/pull/73 with it. function fixpkg(pkg::String, overwrite = false) !isdir(Pkg.dir(pkg)) && error("Did not find package directory") repo = LibGit2.GitRepo(Pkg.dir(pkg)) LibGit2.isdirty(repo) && error("Package repo is dirty") if overwrite info("Checking out branch fix_where") LibGit2.branch!(repo, "fix_where") end for (root, dirs, files) in walkdir(Pkg.dir(pkg)) for file in files if endswith(file, ".jl") FixParameterisedFunctionDeprecation.fixdep(joinpath(root, file), overwrite) if overwrite LibGit2.add!(repo, joinpath(root, split(root, Pkg.dir(pkg))[2])) end end end end overwrite && LibGit2.commit(repo, "fix deprecation warnings for new where syntax") return end

PSA: Parametric method syntax deprecation about to drop

Internals & Design

Keno August 12, 2017, 6:58pm 29

Now done: https://discourse.julialang.org/t/ann-femtocleaner-our-newest-robot-intern

Topic		Replies	Views
Anybody else find the new where syntax less than satisfactory? General Usage	14	8525	December 15, 2019
Using Deprecations.jl (and more generally on updating syntax) General Usage syntax , femtocleaner	5	1204	October 17, 2017
What is the main point of "where"? General Usage	7	1501	May 27, 2017
Warning in 1.0 +? General Usage	28	2051	March 3, 2020
New parametric functions syntax has a readability problem General Usage	11	1797	December 28, 2017

PSA: Parametric method syntax deprecation about to drop

Related topics