-
-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hosc-0.21 breaking changes #1103
Comments
…downgrade because of breaking changes in hosc 0.21 (see issue tidalcycles#1103)
Yes agreed we should stick to hosc-0.20. There's also a tighter version dependency in It would be great to upgrade to hosc-0.21 at some point though, as we're currently preventing its release on stackage commercialhaskell/stackage#7627 Rohan actually uploaded hosc-0.21 on my request, to get rid of an obsolete dependency that caused tidal to be removed from debian: |
What is this tighter dependency that prevents hosc to work with the debian ghc? I tried to compile the latest hosc repo code -- which seems to be at version 0.22 already -- with ghc 9.0.2 and got an error resolved by simply specifying edit: So implementing hosc-0.21/0.22 in Tidal could free the way for hosc into stackage? Is this, plus maybe the bipolar LFO feature you mentioned in #1101, enough for a new Tidal release? |
Just retracing my steps on my laptop with ghc 8.8.4..
It looks like this is down to a change in bytestring-0.11.0.0: Importing from
I don't think the author of hosc Rohan uses github, so will drop him an email.. |
Oops only just read your post properly.. Yep just putting a lower bounds on bytestring on hosc seems to fix it! I'm pretty sure I tried setting the lower bounds in tidal and this didn't work, so I just assumed bytestring was part of core and couldn't be upgraded.. I'll send rohan another email! |
Yes there's quite a lot of other changes waiting for release. What's Changed
|
(oops sorry for pinging everyone!) |
@yaxu, your solution was the better alternative, I guess: #1105 |
closing with PR #1105 |
hosc-0.21 apparently breaks tidal-listener since Functions and Types are now differently created in hosc. E.g.
data OscProtocol
. Maybe Tidal should revert and expect hosc 0.20 for now and either stay there or incorporate the hosc changes into tidal-listener and Tidal itself, which I would volunteer for to do so -- if desired.The text was updated successfully, but these errors were encountered: