updateLookupWithKey bug? Was: Data.Map, Data.IntMap documentation (1611)

[Christian Maeder]

The original documentation only said "lookup and update".

I think it makes more sense to return the old value (i.e. the lookup
result in the original input map.), because the new value can be
recomputed using the update function. The opposite (recomputation of the
old value given the new one) is not possible.

But I agree too, that deprecating this function is the right thing (in
the future).

Cheers Christian

Andriy Palamarchuk wrote:
> Don, I'll leave QuickCheck out of scope for the
> documentation change.
> 
> Adrian, question whether to deprecate
> updateLookupWithKey  is worth discussing, but we need
> to fix the function anyway.
> 
> All my documentation changes are ready. I'm holding
> the patch only for this problem.
> 
> What if I leave the function description for IntMap
> the same as for Map and submit a bug report for the
> problem?
> Then the person resolving the bug will either fix the
> docs or the documentation.
> 
> Any thoughts?
> Andriy
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com