About to start porting kantan.* to scala 2.13. Wish me luck.
-
Show this thread
-
Ah, yes, dependency hell. Need scalacheck > 1.13, but that’s not supported by cats. Also need scoverage to support 2.13.0-RC1. Guess I’m stuck, unless these projects need help with these specific topics?
2 replies 0 retweets 0 likesShow this thread -
Replying to @NicolasRinaudo
Do you think switching to Fury would solve some of them at least?
1 reply 0 retweets 0 likes -
Replying to @Kamugo
Some of them are binary but not source incompatibilities so sure, that’s the whole point, I think. But some are just broken under 2.13, such as scoverage. I have other issues with fury, which I already brought up with
@propensive, and might be show stoppers for my specific needs2 replies 0 retweets 1 like -
Replying to @NicolasRinaudo @Kamugo
Can you remind me what they were, just to remind me whether I addressed them, or just promptly forgot...?
1 reply 0 retweets 1 like -
Replying to @propensive @Kamugo
Plugins. You addressed them very explicitly by stating they were never going to be a part of Fury :)
2 replies 0 retweets 1 like -
Replying to @NicolasRinaudo @Kamugo
Ah yes, that hasn't changed! But plugins aren't a need in themselves... you presumably have some other need which plugins are currently solving, and I'd like to solve that some other way.
1 reply 0 retweets 0 likes -
He mentioned that in response to my question and it's a good use case so I will re-ask: how would you propose to set up static code analysis, test coverage, formatting, linting, wart finders and such with fury?
1 reply 0 retweets 0 likes -
I don't believe code formatting should be part of the build... but someone could write a "compiler" which compiles source code to source code. It just doesn't seem sensible to reformat all your code every time you change anything... before committing, though, sure.
2 replies 0 retweets 2 likes
Almost all the other things you list are just compiler plugins, so you would just depend on them. But static analysis is more interesting. I'm looking at finding sufficiently general solutions to that, or failing that, integrating some of the use cases directly into Fury.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.