Skip Menu |

This queue is for tickets about the Hash-Merge CPAN distribution.

Report information
The Basics
Id: 122879
Status: rejected
Priority: 0/
Queue: Hash-Merge
People
Owner: Nobody in particular
Requestors: ALTREUS [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Wed Aug 23 07:58:12 2017 ALTREUS [...] cpan.org - Ticket created
Subject: Arbitrarily specify merge condition
Would be great to be able to provide a subref that determines which of two conflicting values to keep. Alternatively, to provide merge strategies that consider the values rather than the source of the values (e.g. PRESERVE_GREATEST) In my use case, I'd like to keep the one that specifies a bigger version number, for example.
  Wed Aug 23 08:13:35 2017 REHSACK [...] cpan.org - Correspondence added
On Wed Aug 23 07:58:12 2017, ALTREUS wrote: Show quoted text
> Would be great to be able to provide a subref that determines which of > two conflicting values to keep. Alternatively, to provide merge > strategies that consider the values rather than the source of the > values (e.g. PRESERVE_GREATEST) > > In my use case, I'd like to keep the one that specifies a bigger > version number, for example.
You can already do that. Specify an own behavior, which is always called with the left and the right value and you can decide which one to keep. What is your concrete wish? Do you suggest some more default behaviors? If so, please send also their specifications, since what makes an array bigger or makes a hash greater heavily depends on perspective.
  Wed Aug 23 08:13:35 2017 The RT System itself - Status changed from 'new' to 'open'
  Fri Mar 09 10:50:50 2018 REHSACK [...] cpan.org - Correspondence added
No details given, requested feature already supported.
  Fri Mar 09 10:50:51 2018 REHSACK [...] cpan.org - Status changed from 'open' to 'rejected'