Port summonIgnoring from 3.7 as c.inferImplicitValueIgnoring#11068
Conversation
|
We ought to encourage more tickets and PRs with links to youtube or tiktok! My favorite bit so far is the correct pronunciation of Circe. |
|
correct??
first come first serve! |
|
I tried to get that pedantic line adjusted years ago but wasn't successful. I think pedantry calls for correctness. That could be called "a pedant's mismatch". (I mean the Attic pronunciation.) |
lrytz
left a comment
There was a problem hiding this comment.
LGTM, thanks @MateuszKubuszok and sorry for the delay!
|
Thanks! |
summonIgnoring from 3.7 as c.inferImplicitValueIgnoring
|
@lrytz did you omit this from the 2.13.18 release notes on purpose? |
|
This was already merged for 2.13.17 and is listed in those release notes (https://github.com/scala/scala/releases/tag/v2.13.17) |
This PR backports
Expr.summonIgnoringthat was introduced in 3.7.0.On 3.7.0 it allowed:
However, it increased the maintenance burden on such libraries since they need to implement 2 different hierarchies to keep the behavior consistent. It might also burden users who would like to use such libraries and cross-compile their codebases.
By adding just 1 public macro method - and keeping the behavior and signatures of all the other methods unchanged - libraries that use such solutions to improve the QoL of their users could have once again align how the code looks and behaves, preventing unnecessary friction during the 2->3 migration process.