Closed tomjaguarpaw closed 2 years ago
I'm inclined to agree that we should completely remove the re-exports in the next major release, but can we make a point release first (or indeed "at the same time") containing all the non-breaking changes that it can? That would provide a smoother upgrade path.
I think we should just take the big step now. Splitting it up like this is unlikely to be much better, and I honestly can't see good reason for it. Improvement is long overdue, and this is a very bad legacy decision.
As you wish. I am in support of Bodigrim's comments on #101. Personally I think it it would be preferable for the band aid to be ripped off quickly with respect to the passage of time but slowly with respect to the increase of version numbers. As Bodigrim says, 2.3 can be released at the same time as 2.4. I believe that would provide a smoother experience for users. But ultimately the choice rests with you.
@emilypi I think this has been superceded already?
Yeah - you did write the thing that's true.
If one long term possibility is that we remove certain re-exports from
mtl
modules it seems like the documentation should warn about this. Of course, this is not as good as deprecating the re-exports, but that functionality doesn't exist, and in its absence it seems like this would be an important way to communicate future potential breakage to users.