Add ApplicativeError.redeem and MonadError.redeemWith

[joan38]

No description provided.

[codecov-io]

Codecov Report

Merging #2560 into master will decrease coverage by 0.02%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #2560      +/-   ##
==========================================
- Coverage   95.21%   95.18%   -0.03%     
==========================================
  Files         361      361              
  Lines        6598     6600       +2     
  Branches      280      276       -4     
==========================================
  Hits         6282     6282              
- Misses        316      318       +2

Impacted Files	Coverage Δ
core/src/main/scala/cats/syntax/monadError.scala	88.88% <0%> (-11.12%)	⬇️
.../src/main/scala/cats/syntax/applicativeError.scala	93.75% <0%> (-6.25%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 191fae4...682f318. Read the comment docs.

[kailuowang]

I might've missed something. Is this a shortcut for fa.map(f).handleError(ef)?

[joan38]

@kailuowang Well it's supposed to be in the type class but because of 2.11 bin incompat it's juts in the ops.
This is to match the IO.redeem.

[kailuowang]

Thanks, that clarified the intention for me, I think. The issue is that if we can't add it to type class then we can't have instances to override it, then there isn't much point of adding it before 2.0 with which we shall be able to add it to type class without breaking BC, right?

[joan38]

@kailuowang It probably make sense.
How do we handle stuff that will go in 2.0? Do we keep breaking PRs like this one open?

[kailuowang]

yeah for cases like this , we can add it to the type class, let the mima test fail but schedule it to milesstone 2.0.

[diesalbla]

This PR seems to be doing a very similar thing to @alexandru PR here #2237.

[joan38]

@diesalbla Thanks I'm closing this one