Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jul 27 11:54
    scala-steward closed #295
  • Jul 27 11:54
    scala-steward commented #295
  • Jul 27 11:54
    scala-steward opened #304
  • Jul 13 12:51
    scala-steward closed #302
  • Jul 13 12:51
    scala-steward commented #302
  • Jul 13 12:51
    scala-steward opened #303
  • Jul 11 12:16
    scala-steward closed #287
  • Jul 11 12:16
    scala-steward commented #287
  • Jul 11 12:16
    scala-steward opened #302
  • Jul 05 15:17
    scala-steward closed #291
  • Jul 05 15:17
    scala-steward opened #301
  • Jul 05 15:17
    scala-steward commented #291
  • Jul 05 15:17
    scala-steward opened #300
  • Jul 05 15:17
    scala-steward opened #299
  • Jul 05 15:17
    scala-steward closed #296
  • Jul 05 15:17
    scala-steward commented #296
  • May 10 16:05
    scala-steward opened #298
  • Apr 07 14:05
    scala-steward opened #297
  • Apr 04 22:04
    scala-steward closed #289
  • Apr 04 22:04
    scala-steward commented #289
Alec Zorab
@AlecZorab
Gotcha. The CI server won't love it, but it's a decent enough workaround for development. I'll give it a go
Alexandre Archambault
@alexarchambault
@ijuma argonaut-shapeless 0.2.0-SNAPSHOT on sonatype now depends on shapeless 2.2.0 final - I'll do a release soon (should be in the coming days)
Ismael Juma
@ijuma
@alexarchambault thank you
Miles Sabin
@milessabin
@alexarchambault thanks :-)
Alexandre Archambault
@alexarchambault
@/all Just published argonaut-shapeless 0.2.0, which is simply an update to shapeless 2.2.0.
Alexandre Archambault
@alexarchambault
Development will go on towards 0.3.0, with hopefully support for shapeless 2.2 orphan derivation, and more varied / customisable codecs (ability to change the way products are encoded - e.g. to transform the keys' case, or to put the product in a json array rather than an object, or change the way coproducts are encoded - e.g. to encode eithers directly as their right or left values rather than nesting them in { "Left" / "Right": ... }, or to add a custom field for the type, ...)
(see the discussion here: alexarchambault/argonaut-shapeless#5)
Ismael Juma
@ijuma
@alexarchambault awesome
Miles Sabin
@milessabin
Fantastic ... thanks :-)
Miles Sabin
@milessabin
WRT customisable codecs, I'm open to having a parameterized variant of LabelledGeneric in shapeless ... IIRC you were asking for that a while back?
Alexandre Archambault
@alexarchambault
You're welcome :-)
Alexandre Archambault
@alexarchambault
@milessabin About variants of LabelledGeneric, I'm less opiniated about it now. If this can be handled in a slick way from shapeless, let's go for that. But libraries using labels can handle it directly else.
Miles Sabin
@milessabin
Are you going to be in Amsterdam next week?
Alexandre Archambault
@alexarchambault
@milessabin Nope, I wasn't expecting tickets to get sold out that early :-(
Miles Sabin
@milessabin
:-(
Miles Sabin
@milessabin
Any ETA on a release with orphan handling?
ie. something along the lines of test/orphans.
Alexandre Archambault
@alexarchambault
@milessabin milessabin/shapeless#391 was blocking me the last time I tried
It's either cachedImplicit or orphans :-(
Miles Sabin
@milessabin
Gotcha.
OK, I'll take a look at milessabin/shapeless#391 and get back to you.
Alexandre Archambault
@alexarchambault
Thanks
Miles Sabin
@milessabin
I've just pushed a fix for milessabin/shapeless#391 ... it'll show up in the next 2.2.3-SNAPSHOT.
Alexandre Archambault
@alexarchambault
@milessabin Thanks! I didn't know if the could just be replaced by implicitly like you did, in the fix, I though it was somehow required.
Miles Sabin
@milessabin
the would refine the type more that implicitly, but there's no way that we can use that here, so there's no benefit to be gained from using the.
Alexandre Archambault
@alexarchambault
I hadn't admittedly though much about it :-)
Miles Sabin
@milessabin
I still have no idea why the isn't working in that context. But I don't want to hold up an argonaut-shapeless release because of that.
Alexandre Archambault
@alexarchambault
@milessabin Both scalacheck-shapeless and argonaut-shapeless (branch 0.3.x) are now fine with orphan derivations. Thumbs up for shapeless 2.2.3.
Miles Sabin
@milessabin
Awesome!
I'm working on a Generic1 bug and I'll release as soon as I have a fix for that. Fingers X'd today or tomorrow :-)
Miles Sabin
@milessabin
2.2.3 released :-)
Alexandre Archambault
@alexarchambault
{scalacheck/argonaut}-shapeless releases in a few hours :-)
Miles Sabin
@milessabin
Awesome :-)
Alexandre Archambault
@alexarchambault
@/all Just published 0.3.0, targetting shapeless 2.2 (>= 2.2.3), with proper support for shapeless orphan derivation.
Alexandre Archambault
@alexarchambault
New developments of :point_up: June 4 2015 3:20 AM will be for 0.4.0
Miles Sabin
@milessabin
:sparkles: :fireworks: :clap:
Miles Sabin
@milessabin
@alexarchambault could you try out the latest shapeless snapshot ... I've fixed your nested ADT issues.
Alexandre Archambault
@alexarchambault
@milessabin Thanks! I'll try asap.
Miles Sabin
@milessabin
Ta :-)
Alexandre Archambault
@alexarchambault
@milessabin A quick update about nested Json (alexarchambault/argonaut-shapeless#9), I ran into what's described here,
that is different implicits being derived by Lazy compared to implicitly. Namely, implicitly find implicits from argonaut.Argonaut, whereas Lazy apparently tries to derive these as ADTs, not viewing those of argonaut.Argonaut, and fails.
Miles Sabin
@milessabin
Yes, I'm having similar problem right now.
Alexandre Archambault
@alexarchambault
In what context?
Miles Sabin
@milessabin
Deriving orphans for Cats.
The orphan derivation mechanism only appears to be lowering the priority of derived instances at the top level, not in nested contexts ... is that what you're seeing?
Alexandre Archambault
@alexarchambault
Not exactly. I'm having the same error with or without orphan derivation.
Lazy seems not to derive the same thing as just implicitly
Miles Sabin
@milessabin
Lazy doesn't derive anything ... it just suppresses divergence.
Alexandre Archambault
@alexarchambault
Yes, I mean: implicits found with implicitly are fine (checked with reify), trying to get the same implicits with Lazy.mkLazy fails
The error says that the macro expansion tries to use types that are private[argonaut], sub-types of argonaut.Json
But these shouldn't be involved. They are not when using just implicitly, as reify confirms.
Miles Sabin
@milessabin
Hmm ... interesting.