Closed mcabbott closed 2 years ago
Base: 93.14% // Head: 91.61% // Decreases project coverage by -1.52%
:warning:
Coverage data is based on head (
bfd2e71
) compared to base (e5cb9c2
). Patch has no changes to coverable lines.
:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
Ya thank you for this! I'll add this and update the package. The package is going to undergo an overhaul soonish but at least things will work on 1.9 now.
Great!
Would you mind tagging a release? This will remove it from the list of problems seen by PkgEval when scanning the ecosystem for what 1.9 breaks.
Done!
I don't know anything about this package but tests now pass locally.
The reason for suggesting this change is that Base exports
stack
from 1.9, creating a clash:In fact DataFrames also exports
stack
, so there may already be a clash if those are used together. Recent versions of DataFrames extend the function from Compat / Base to avoid this, and this package depends on DataFrames, so an obvious solution would be to import and extend that: Then this package needs no new deps.But latest DataFrames wants Compat 4, and this wants HDF5 0.15, which wants Compat 3. So this PR proposes to, first, allow HDF5 v0.16. I don't know what the changed or whether it matters: https://github.com/JuliaIO/HDF5.jl/releases/tag/v0.16.0
The method defined here is for a type this package owns, so this is not piracy:
https://github.com/ptiede/VIDA.jl/blob/e161a11b07b1cac5272f708b1f663fd582a34e99/src/templates/composite.jl#L58-L60
And looking at the other methods, there is no reason to expect ambiguities:
Also, the earliest DataFrames version listed does already contain (and export) this function.