Skip to content

Conversation

martinholters
Copy link
Member

Compat dropped support for Julia versions prior to v1.6 about 14 months after it was released, 6 months after it became LTS (by the release of 1.7). As v1.10 has been released about 13 months ago and became LTS about 5 months ago, we can start thinking about dropping support for versions prior to v1.10. Which this PR does.

Seizing the opportunity of a major version bump, this does another change that might be worth more discussion: It resolves #814 by applying it to the few remaining offenders. Maybe this PR - threatening to actually have an impact - receives more feedback than #814... If there are objections, I happily remove the last two commits to reduce this to the minimum-required-version-bump only.

@lgoettgens
Copy link

I am really in favor of getting rid of the type piracy like your are doing here.

One minor comment: In the feature overview at https://github.com/JuliaLang/Compat.jl/tree/mh/deprecate-type-piracy?tab=readme-ov-file#supported-features, it looks a bit weird that insertdims and logrange don't need a Compat. qualification. Would it make sense to make sense to try to unify how to use Compat.jl's different features by not exporting these two (but instead making them @compat public)? No strong opinion either way, but I wanted to point it out anyway.

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.

Avoid type piracy by defining distinct functions
2 participants