Closed michalrus closed 5 years ago
I guess so, given this instance: https://github.com/nikita-volkov/focus/blob/409950dfefaa070b1d77b2a72c01fcb4d2a310e7/library/Focus.hs#L22-L39 … but it’s so misleading…
I much preferred the previous design, which was explicit in not eating my inserts.
I would prefer the current one, if such silent bugs were impossible…
Halp.
E.g. now, how do I implement a replace
to set a new v
for a given k
, but return the previous Maybe v
?
Any immediate way that comes to mind will have this bug, and worst of all, it will compile…
This is a bug in implementation of "focus". Thanks for reporting. It might take me a few days to fix.
Oh, I thought that was on purpose. Can’t wait, then, to see the new implementation. =) Great, thanks!
The issue is fixed in "focus-1.0.1.3". However I can't release yet, because Hackage is down today.
Thank you very much!
Published.
Hi,
I was bumping dependency versions and noticed this:
resulting in:
That’s kind of unexpected, given that the code compiles, and the
Focus
docs say:Is this really an expected behavior with this composition? If so, why is it useful?