Closed ckipp01 closed 1 year ago
Do you know if this is an intrinsic limitation of Scala 3 or if it can be fixed? I think the end goal is to have feature parity between Scala 2 and 3
Do you know if this is an intrinsic limitation of Scala 3 or if it can be fixed? I think the end goal is to have feature parity between Scala 2 and 3
To be honest I'm not sure without digging in. I did quickly try to add in a check for DefDef
s here:
But then it screwed up the next line so I didn't go further. My guess is that it's totally doable. So if you'd rather hold off on this, I can try to dig into that and actually fix it correctly if that'd be preferable.
My feeling is more that we should not close the issue if it's an actual issue, instead maybe add more info about what is the actual limitation. This means that we can probably merge this (after removing "Closes #257" from the PR description, so the original issue remains open).
My feeling is more that we should not close the issue if it's an actual issue, instead maybe add more info about what is the actual limitation. This means that we can probably merge this (after removing "Closes #257" from the PR description, so the original issue remains open).
Sure, I put some more info in the issue and I remove the "closed". If I get a bit more free time this week I'll try to dig into a fix.
Thank you for your contribution @ckipp01 ! :)
In Scala 2 you could use a
def
to define yourcls
s, but in Scala 3 the implementation is only looking forvalDef
s in the file, meaning thatdef
s will no longer work. This makes sure the docs don't mention usingdef
s and instead focus the verbiage onval
s.