Marnick L'Eau
Marnick L'Eau
Alternative: return RuntimeException instead of T so we can `throw Unchecked.throwChecked(ex);` instead of `return Unchecked.throwChecked(ex)`, just to shut the compiler up about control flow not ending. Might work better with...
throw Unchecked.throwBack throw Unchecked.returnThrow/throwReturn throw Unchecked.feignReturning fake, false, out, pretend, escalate, reciprocate, echo, mirror, break, elevate, subvert, overcharge, dissent, hide, disguise... Just throwing some words that come to mind for...
throwThenReturn? But it won't even actually return anything because it will throw first, so the name would need to be throwAndFeignReturn or feignReturnButActuallyThrow or something. I feel like expressing every...
Oh, and I would like to bring up the initial `return (T) null` idea again. There's a usecase for it: ```java Map mappers = new HashMap(); mappers.put(A.class, a -> foo(a));...
> that auto-boxing will be performed (but never executed). It can't ever be executed because an exception will be thrown first... And since how many versions ago does java autobox...
I think Unchecked.throwAndReturn is about as good as it gets. It's short, says exactly what it will do, and has no redundant wording (throwAndReturnUnchecked is a bit too verbose if...
Honestly, I don't think anyone will be confused because of that :/ And if someone is, they can see at a glance what it does when they open the source...
Doesn't the HTTP Observer feature take care of this?
I ran into this issue when resorting to what I hoped would be a workaround (the umpteenth already while trying for months to get a project onto yarn+pnp without breaking...
I finally got the notification settings fixed and enabled ditto to create them again. It seems it's already programmed to only notify once as long as the process runs. This...