Scala 2.13 artifact? about matryoshka HOT 1 OPEN

Okay so… It is with heavy heart that I need to convey this.

We've decided to begin the process of winding this project down. That process is not likely to conclude any time soon though since Quasar (and many of our other internal projects) are heavily dependent on it, we're just less dependent on it than we used to be, given some of the shortcomings of recursion schemes as an approach for encoding many algorithms.

This is all rather tangled though, because unfortunately we're also not on the latest version of Matryoshka, since many of the encodings have changed and the upgrade is likely more disruptive than it's worth, given the existence of Droste. Oh, and nothing is published for 2.13 (as this issue notes), yet we're trying to upgrade internally to 2.13, which brings us to today.

The right thing to do would be for us to upgrade to Matryoshka 0.21.8, then release 0.21.9 cross-published for 2.13, then proceed forward. Unfortunately, there isn't enough time available for us to do the right thing, and the investment doesn't pay dividends when we're mulling moving over to Droste anyway. :-( So we're going to do the wrong thing.

The wrong thing, in this case, is we're going to cross-publish the 0.18.x line for Scala 2.13, because that represents the absolute shortest path towards getting our internal things working. I realize this sucks for… well actually pretty much everyone. Once I have gotten cross publication working for 0.18, I will take a flier at 0.21.x just to see if I can make it happen. @davidhoyt's work on upgrading all the things will probably actually make it much easier than it will be to get 0.18 cross-publishing. So in a best-case scenario, we should have cross-builds for 0.18 and for 0.21.

Long-term, I don't see this project continuing beyond 0.21. We expect to migrate to Droste, likely sometime this year, depending on other factors.

from matryoshka.