LoadOrCompute error handling

[mattjohnsonpint]

#103 describes how to raise an error if Compute fails. In that example, return 0, true ensures that the 0 is not added to the map.

That works fine for Compute, but I don't see a similar approach possible for LoadOrCompute - since the valueFn doesn't have a delete return value.

So, when using LoadOrCompute, how can I ensure that if an error occurs that I don't add a zero value (or nil, etc.) to the map? I wouldn't want a concurrent thread to retrieve that and treat it as an actual good value.

TLDR: Can you please add a version of LoadOrCompute that accepts a valueFn func() (newValue V, delete bool)?

Thanks.

[puzpuzpuz]

Compute is flexible enough to be used in LoadOrCompute style, so you could use it instead of LoadOrCompute:

counts := xsync.NewIntegerMapOf[int, int]()

v, ok := counts.Compute(42, func(oldValue int, loaded bool) (newValue int, delete bool) {
	if loaded {
		return oldValue, false // return the existing value
	}
	// the error-aware logic goes here
	return
})

Does this make sense?