I've been flattered by all the #ScalaThankYou messages this week, but they've revealed to me that there are many more people than I realised quietly using Magnolia for generic derivation! If you're using it and I might not know you are, please let me know so I can compile a list!
-
-
Happy user in Caliban! There's only 1 thing that could be improved: error reporting. When there are many chained implicits involved (deeply nested case classes), errors get cryptic. Ideally it would tell exactly which deeply nested type is missing an instance.
-
Have you seen the derivation "stack traces", like the one 2/3 of the way down this page: https://propensive.com/opensource/magnolia … ? These don't appear if you're deriving implicitly, but if you explicitly request a derivation (e.g. something like Type.gen[Type]), you should see it.
- Show replies
New conversation -
-
-
I tried quickly but had issues I failed to diagnose (probably with implicit namespace pollution) so I went back to shapeless Now I hope to have the time to give it a stab again, as I am drowning in implicit namespace pollution issues anyway

-
now, Kaleidoscope, that on's on top of the toolbox right next to the screwdrivers.
- Show replies
New conversation -
-
-
Thank you, Jon! Some most cuttie parts of Magnolia were shamelessly copied and reused in our libs: https://github.com/search?q=%22copied+from%22+%22https%3A%2F%2Fgithub.com%2Fpropensive%2Fmagnolia%22&type=Code …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.