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

Add Scala Native support for core #105

Closed
wants to merge 1 commit into from
Closed

Add Scala Native support for core #105

wants to merge 1 commit into from

Conversation

lolgab
Copy link
Contributor

@lolgab lolgab commented Jul 27, 2019

Superceded by #106

Remove specs2-scalacheck test dependency from core
Rewrite core Specification in plain Scalacheck

Remove specs2-scalacheck test dependency from core
Rewrite core Specification in plain Scalacheck
Copy link
Member

@rossabaker rossabaker left a comment

Choose a reason for hiding this comment

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

Thanks!

I'd say priority for the ecosystem is releasing discipline-1.0.0 so we can release cats-2.0.0. I'd prefer we move on #106 first, which will cause a couple of light merge conflicts here. I commented on where I anticipate them. But I also don't see any reason that this would be incompatible with being introduced in a subsequent 1.x release.

@@ -1,9 +1,27 @@
language: scala
dist: trusty
Copy link
Member

Choose a reason for hiding this comment

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

trusty is EOL. We'd want xenial, which I just switched to in #106.

@@ -102,18 +111,27 @@ lazy val root = project.in(file("."))
specs2DisciplineJVM
)

lazy val discipline = crossProject(JSPlatform, JVMPlatform)
lazy val discipline = crossProject(JSPlatform, JVMPlatform, NativePlatform)
Copy link
Member

Choose a reason for hiding this comment

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

I just renamed this to core in #106. Didn't think it would make work for anyone. Oops.

Copy link
Contributor Author

@lolgab lolgab Aug 2, 2019

Choose a reason for hiding this comment

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

I'll rebase it on top and use the new names.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Is it ok to wait for #106 to be merged? I can put my changes on top of it then.

for additive groups ${additiveGroup}
for multiplicative groups ${multiplicativeGroup}
"""
class DisciplineSpec extends Properties("A RuleSet should compute the properties correctly") {
Copy link
Member

Choose a reason for hiding this comment

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

👍 This looks like a positive change, with or without scala-native support. It uses a dependency already on hand.

Copy link
Contributor

Choose a reason for hiding this comment

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

Could somebody please provide this part as an extra PR? Happy to merge that now.

@larsrh
Copy link
Contributor

larsrh commented Aug 2, 2019

First of all, @lolgab, I would like to thank you for this contribution. I appreciate you working on scala-native support. Now the "but" part. I'm a little concerned about using a forked dependency of ScalaCheck. There's currently a discussion on its future maintenance, and I'd like to at least wait for this. If it still turns out to be impossible to get the native support merged upstream, we can talk again.

PS: I'm happy to be overruled by other Typelevel members on this.

@lolgab
Copy link
Contributor Author

lolgab commented Aug 3, 2019

I don't like the use of a forked artifact too. I tried to ask on scalacheck gitter, on the github issue but nobody of the maintainers published the Scala Native artifact. (Scala Native support is merged on master branch of Scalacheck, it's only giving scalacheckNative/publishSigned).
If you know any Scalacheck maintainer you could try to ask for an artifact (I would be very thankful in that case 🙏 😃)

@larsrh
Copy link
Contributor

larsrh commented Aug 3, 2019

As far as I know (from what @non said) only Rickard currently can run releases.

@larsrh
Copy link
Contributor

larsrh commented Sep 21, 2019

1.14.1 with Scala Native support is out. I'll pick up this PR again.

@larsrh larsrh mentioned this pull request Sep 21, 2019
@larsrh larsrh closed this Sep 21, 2019
@lolgab lolgab deleted the scala-native-support branch September 22, 2019 08:46
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