These are chat archives for lift/framework

19th
Mar 2017
Matt Farmer
@farmdawgnation
Mar 19 00:24
@Shadowfiend The extractor.
Antonio Salazar Cardozo
@Shadowfiend
Mar 19 00:24
Phew :D
Yeah it looks pretty gnarly. Though a rewrite would also be turbo-gnarly.
Matt Farmer
@farmdawgnation
Mar 19 00:25
I sent a note to the list about it earlier
And just sent a follow up explaining I meant extractor :P
Yeah, so I think that scala.reflect is probably to the point where we could lean on that instead of the mess that we do now.
We primarily do Java reflection but then special case a bunch of spots where that doesn’t work.
It’s made my tuple implementation pretty much impossible.
Antonio Salazar Cardozo
@Shadowfiend
Mar 19 03:09
Not really. Scala.reflect isn't the thing that'll be the thing anymore. Scala.meta is, and it's not considered done or stable yet.
(At least last I heard.)
Say what you will about the current extractor, but in 95% of cases it works, and in another 1% it's relatively straightforward to make it work, and that's with no development effort in some time. Those are some pretty big votes in its favor.
We could probably develop a parallel scala.meta-based extractor for optional use though.
Will post some ruminations on the list when I get a chance.