Skip to content
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

Update MiMA and fix issues it noticed. #44

Merged
merged 9 commits into from
Nov 18, 2019
Merged

Conversation

non
Copy link
Collaborator

@non non commented Nov 18, 2019

We want compatibility with 0.3.0, so I updated the plugin, updated the version
to be checked (was 0.2.4 which meant lots of bogus incompatibilities were
reported) and then fixed the issues.

We want compatibility with 0.3.0, so I updated the plugin, updated the version
to be checked (was 0.2.4 which meant lots of bogus incompatibilities were
reported) and then fixed the issues.
@non
Copy link
Collaborator Author

non commented Nov 18, 2019

You can verify with coreJVM/mimaReportBinaryIssues.

@non
Copy link
Collaborator Author

non commented Nov 18, 2019

Once this lands I want to do a release for Scala 2.13.

@johnynek
Copy link
Collaborator

Looks good but CI failed.

After we merge this and when we next need to break we should remove that compatibility method since the name is brutal.

@codecov-io
Copy link

codecov-io commented Nov 18, 2019

Codecov Report

Merging #44 into master will decrease coverage by 1.86%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #44      +/-   ##
==========================================
- Coverage   84.57%   82.71%   -1.87%     
==========================================
  Files          13       13              
  Lines         376      376              
  Branches       20       16       -4     
==========================================
- Hits          318      311       -7     
- Misses         58       65       +7
Impacted Files Coverage Δ
core/src/main/scala/com/stripe/dagon/Dag.scala 85.64% <ø> (ø) ⬆️
core/src/main/scala/com/stripe/dagon/Expr.scala 55.17% <100%> (-10.35%) ⬇️
core/src/main/scala/com/stripe/dagon/Literal.scala 50% <0%> (-11.77%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 69d0aa4...deb7d7e. Read the comment docs.

@non
Copy link
Collaborator Author

non commented Nov 18, 2019

@johnynek A lot of these updates are to get MiMA and Travis working, but the rest are to get ready for trying to support Scala 2.13.

We're going to have to decide what to do about Stream since we do use it. Honestly I'm tempted to call this 0.4.0 and break bincompat just so we can get out of having Stream in our public API. What do you think?

@johnynek
Copy link
Collaborator

Sure, I think that’s fine. Let’s do 0.4.0 and minimize hacks.


lazy val commonJvmSettings = Seq(
testOptions in Test += Tests.Argument(TestFrameworks.ScalaTest, "-oDF"))

lazy val commonJsSettings = Seq(
scalaJSStage in Global := FastOptStage,
parallelExecution := false,
requiresDOM := false,
jsEnv := new org.scalajs.jsenv.nodejs.NodeJSEnv(),
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

isn't this line duplicated below?

@@ -833,7 +832,8 @@ class DataFlowTest extends FunSuite {
if (incs <= 0) f
else incrementChain(f.map(_ + 1), incs - 1)

val incCount = if (catalysts.Platform.isJvm) 10000 else 1000
//val incCount = if (catalysts.Platform.isJvm) 10000 else 1000
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think testing this with 1000 destroys the test. This is about the stack, I think... but we can deal with it later.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, catalysts isn't published for 2.13 so I was gonna disable this then try to fix it.

def com$stripe$dagon$Dag$$copy$default$2(): com.stripe.dagon.FunctionK[N, Literal[N, ?]] =
self.toLiteral

def com$stripe$dagon$Dag$$copy$default$3(): scala.collection.immutable.Set[Id[_]] =
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I bet if you make these private[paiges] it is still binary compatible but no one in scala can see them. What do you think about that?

Copy link
Collaborator

@johnynek johnynek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@non non merged commit 01b5697 into master Nov 18, 2019
@non non deleted the topic/restore-bincompat branch November 18, 2019 18:26
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.

3 participants