Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Dec 06 02:38
    ekrich commented #1064
  • Nov 27 17:16
    ekrich synchronize #1637
  • Nov 27 01:26
    ekrich commented #1637
  • Nov 27 01:24
    ekrich synchronize #1637
  • Nov 26 20:16
    LeeTibbert commented #1635
  • Nov 26 19:35
    ekrich commented #1635
  • Nov 26 19:29
    LeeTibbert commented #1635
  • Nov 26 19:21
    LeeTibbert commented #1635
  • Nov 26 18:28
    LeeTibbert commented #1635
  • Nov 26 15:58
    ekrich commented #1635
  • Nov 26 09:13
    avdv commented #1635
  • Nov 25 21:42
    avdv commented #1635
  • Nov 25 21:41
    avdv commented #1635
  • Nov 25 20:52
    avdv commented #1635
  • Nov 25 20:37
    avdv commented #1635
  • Nov 25 20:36
    avdv commented #1635
  • Nov 25 20:35
    avdv commented #1635
  • Nov 25 18:12
    ekrich commented #1635
  • Nov 24 22:14
    LeeTibbert commented #1635
  • Nov 24 21:21
    LeeTibbert commented #1023
Adam Warski
@adamw
yeah I brought the ! back, putting them in ()
but tests still fail ;)

maybe somebody will have some idea on what I broke here: softwaremill/sttp@5af98b1

I'm getting a lot of java.lang.RuntimeException: Command failed with status URL_MALFORMAT

Maybe @pcejrowski , who originally wrote the code? :)

Richard Whaling
@rwhaling
my hunch is that curl_setopt is mangling the url
Richard Whaling
@rwhaling
oddly, curl_setopt is actually a vararg function, although it only ever takes 3 arguments
and SN 0.4 had some breaking changes to vararg handling
Adam Warski
@adamw
as far as I can see it delegates to
@name("curl_easy_setopt")
  def setopt(handle: Ptr[Curl], option: CInt, parameter: Any): CInt = extern
so no varargs
but maybe sth else changed...
Richard Whaling
@rwhaling
yeah that's the weird thing -
SN 0.4 totally reworked vararg handling along with the C interop, and it changed how some of these edge cases get handled.
you could try something like parameter: Ptr[Byte], but then you'll either need to do a gross cast on int/flag arguments,
or you can define two different bindings to the same C function:
@name("curl_easy_setopt")
  def setopt_int(handle: Ptr[Curl], option: CInt, parameter: Int): CInt = extern

@name("curl_easy_setopt")
  def setopt_ptr(handle: Ptr[Curl], option: CInt, parameter: Ptr[Byte]): CInt = extern
but both are a bit intrusive, might be worth verifying the underlying cause if possible
Adam Warski
@adamw
@rwhaling thanks a lot for your help, but unfortunately I can't get this to work
I've disable the scala-native backend for now, though if anybody would like to work on re-enabling it, I've created an issue: softwaremill/sttp#376
Richard Whaling
@rwhaling
thanks for taking a look @adamw!
Adam Fraser
@adamgfraser
Is there a Scala Native implementation for java-time?
Or a way to use one of the ScalaJS ones?
Richard Whaling
@rwhaling
I think @ekrich has worked on that some
Lorenzo Gabriele
@lolgab
Hi @adamgfraser You can give a look at this: https://github.com/akka-js/scalanative-java-time What version of SN are you using?
Adam Fraser
@adamgfraser
@lolgab 0.4.0-M2
Adam Fraser
@adamgfraser
Looks like it is only published for 0.3. Would it be possible to publish a version for 0.4? Or @rwhaling should we consider downgrading to 0.3 in ZIO? I don't know how much we are giving up by doing that.
Richard Whaling
@rwhaling
@adamgfraser I don't think downgrading to 0.3 will work - we added a bunch of stuff in the 0.4 series to support Zio
it probably makes the most sense to get an 0.4.0-M2 version of that time library published, even if it's from a fork - most of the SN community has moved to 0.4.0-M2 already
Eric K Richardson
@ekrich
@adamgfraser I use the Scala.js version to make up for some small missing pieces needed for the ekrich/sconfig project. I added the few pieces needed to Scala Native but this is a temporary solution. @LeeTibbert and I have talked to @cquiroz about his library https://github.com/cquiroz/scala-java-time as well but there are locale or other issues making it hard to port to Scala Native and keeping JVM support seems to be a goal of his project. Maybe the best approach is to make https://github.com/scala-js/scala-js-java-time work with both JS and Native if @sjrd agrees.
S├ębastien Doeraene
@sjrd
scala-js-java-time is sort of on life support. cquiroz's scala-java-time is more complete, I believe.
Eric K Richardson
@ekrich
@sjrd Ok, good to know - we only really need one but scala-js-java-time is working fine for me. I was thinking that because everytime we looked into it for Scala Native there was a blocker given his library was used on JVM pre version 8 when java.time was introduced.
Adam Fraser
@adamgfraser
Yes. ZIO moved from scala-js-time to -scala-java-time because of the lack of support in scala-js-java-time for some of the data types we were using, particularly ZoneId if I remember correctly.
So I think at least for ZIO this is a blocker in providing support for Scala Native. We have the minimal support thanks to the fantastic work of @rwhaling but if users actually want to do anything with it they are going to need a java-time dependency that works on Scala Native which it sounds like we don't have right now.
Eric K Richardson
@ekrich
Thanks for the info.
Corey O'Connor
@coreyoconnor
Is there a small task (dev or review) I can contribute to? I checkout out: https://github.com/scala-native/scala-native/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22 tho that seems out of date :)
Eric K Richardson
@ekrich
Yeah, that one is still in limbo and some of the methods could be added to Scala.js as well. I put a comment on that one.
Corey O'Connor
@coreyoconnor
@ekrich OK. I see the reference to scala-native/scala-native#1653
I'll see about getting that working :) I'm still somehwat out of commission so no promises tho :(
Eric K Richardson
@ekrich
There are probably more fun things to work on - you had just mentioned that PR and when I looked I saw that there were no references to the work I started. I just had other things I was working on so hadn't gone back to it.
Corey O'Connor
@coreyoconnor
Looks to be: Analyze and measure the load method. In particular on allocation behavior. Optimise (add tests as required). Correct?
that's pretty fun for me ;)
Eric K Richardson
@ekrich
Also, stensorflow got an update but since it requires native C code - it would have to wait for - scala-native/scala-native#1637
Lorenzo Gabriele
@lolgab
Good stuff Eric :)
Do you plan to write some Value classes interface around sblas?
Eric K Richardson
@ekrich
I would like to but it seems it would be a pretty big project and I would need to study what has been done in that space too.
LeeTibbert
@LeeTibbert
re: cquiroz's scala-java-time is more complete At the top of the parabola, I had the core of @cquiroz 's scala-native-time working with scala-native in a private sandbox. As I spent more time to implement the missing functions in the outstanding Issue,
LeeTibbert
@LeeTibbert

ran up against the fact that, IMHO, any version of code which would pass review would require Java default methods in traits. Those are implemented in Scala 2.12 JVM but not in SN. Scalatest was pending, but not released, for SN then. Scalatest might be
available now.

It looked to me like some SN code would be needed to access the Olson time files directly, where available (in libmumble.so). From
a "not having done a trial implementation" view from afar, it looked like a Small Matter of Programming.

As I noted in the Issue, these days the issue is on the back burner for me.

More like, in the refrigerator than on the stove at all.
Eric K Richardson
@ekrich
@LeeTibbert The concern I have is that today only a JS and Native version is needed not one for the JVM for Java 6 and Java 7 so we really need one geared towards only those 2 platforms. I don't see a logical solution without a fork or an enhancement of the Scala.js version.