Scala-native support

Question

Scala-native support

francisdb opened this issue 6 years ago · comments

Francis De Brabandere commented 6 years ago

I was looking at using some parts of akka-http but it seems that the underlying akka-parse is embedding parboiled2 and shapeless. Shapeless is available for scala-native so only parboiled2 remains.

This would for now limit parboiled2 to scala 2.11 as scala-native 0.4.x with scala 2.12 support is not yet available. But that should be no problem as the current base platform is 2.10.

Looks like everything compiles without problems on scala native, only the specs2 dependency is an issue.

Francis De Brabandere · Answer 1 · Sat Feb 23 2019 00:22:18 GMT+0800 (China Standard Time)

@xuwei-k I see you already requested scala native upstream etorreborre/specs2#591

Francis De Brabandere · Answer 2 · Sat Feb 23 2019 00:25:55 GMT+0800 (China Standard Time)

Any chance a native release could be pushed without the tests having run?

Mathias · Answer 3 · Mon Feb 25 2019 17:11:50 GMT+0800 (China Standard Time)

To be honest, I have moved off specs2 and towards Scalatest or even @lihaoyi's utest on all my newer projects. So, if the specs2 dependency becomes a liability for a potential support of scala-native then I'd support a switch of test infrastructure to sth else.
That shouldn't be hard to do at all since, AFAIK, there is nothing specs2-specific that we really depend on in the tests...

Francis De Brabandere · Answer 4 · Tue Feb 26 2019 18:52:03 GMT+0800 (China Standard Time)

Indeed the fastest path here would be switching testing frameworks, so which test framework would you prefer?

Francis De Brabandere · Answer 5 · Tue Feb 26 2019 18:59:00 GMT+0800 (China Standard Time)

I see there is one test using ScalaCheck, that is not yet released for scala native

Mathias · Answer 6 · Tue Feb 26 2019 19:01:26 GMT+0800 (China Standard Time)

I think we should move to https://github.com/lihaoyi/utest.
It does all we need and doesn't get in the way.
And the one test currently relying on ScalaCheck can surely be easily rewritten to a custom generator as well...

Lorenzo Gabriele · Answer 7 · Wed Feb 27 2019 17:09:34 GMT+0800 (China Standard Time)

I've published the artifact under my groupid having seen no interest about Scala Native by scalacheck maintainer. You can use "com.github.lolgab" %%% "scalacheck" % "0.4.1" as Scala Native dependency on other libraries.

Francis De Brabandere · Answer 8 · Wed Feb 27 2019 21:43:25 GMT+0800 (China Standard Time)

Let's see if I can get these tests ported to utest

looks like the utest-scalacheck example at com-lihaoyi/utest#2 might allow to keep the scalacheck part (using @lolgab 's release)

Francis De Brabandere · Answer 9 · Wed Feb 27 2019 21:47:13 GMT+0800 (China Standard Time)

@sirthias should I start from the release-2.1 branch?

Mathias · Answer 10 · Wed Feb 27 2019 21:50:31 GMT+0800 (China Standard Time)

@francisdb Yes, the release-2.1 branch really should be the master...
The master is essentially a failed (due to capacity restriction on my side) attempt to pull the library to the next level.

Francis De Brabandere · Answer 11 · Thu Feb 28 2019 01:14:42 GMT+0800 (China Standard Time)

@sirthias the parboiled - macro seems to conflict with the parboiled - macro, any hints on how I can workaround that?

(I have a not so pretty workaround, will keep a TODO comment in the PR)

Mathias · Answer 12 · Thu Feb 28 2019 03:19:04 GMT+0800 (China Standard Time)

Sorry, @francisdb, I don't understand you question...

Francis De Brabandere · Answer 13 · Thu Feb 28 2019 03:28:21 GMT+0800 (China Standard Time)

@sirthias I understand you don't understand, you will see what I mean once the PR is ready