Skip to main content

How to compare two generic dictionaries

Zilele acestea mi-a fost pusa urmatoarea intrebare:
Intr-un unit test care este cea mai buna modalitate de a compara doua colectii?

Daca va aduceti aminte, in urma cu cateva saptamani am discutat despre CollectionAssert. Aceasta contine o metoda denumita AreEquivalent, care verifica daca doua colectii sunt echivalente. Testul o sa treaca de acest assert daca:
  • numarul de elemente este egal
  • cele doua colectii contin aceleasi elemente( indiferent de ordinea in care apar)
Doua elemente din colectie sunt egale nu daca puncteaza spre acelasi element ci daca sunt egale prin continut( se apeleaza metoda Equals, pentru a face aceasta verificare). In cazul nostru, metoda AreEquivalent o sa itereze prin intreaga colectie de element KeyValuePair pe care un dictionar le contine.
Dictionary<string,string> collection1=new Dictionary<string, string>();
Dictionary<string, string> collection2 = new Dictionary<string, string>();
...
CollectionAssert.AreEquivalent(collection1,collection2);
In cazul in care avem nevoie in cod sa comparam doua dictionare putem sa face in felul urmator:
collection1
.OrderBy(i => i)
.SequenceEqual(collection2.OrderBy(i => i));
Varianta de mai sus este O(n*log(n)). In cazul in care vreti o solutie in O(n), puteti sa incercati o implementare asemanatoare cu aceasta:
public class CollectionComparer<T> : IEqualityComparer<IEnumerable<T>>
where T : class
{
public bool Equals(IEnumerable<T> collection1, IEnumerable<T> collection2)
{
if ((collection1 == null && collection2!=null)
|| (collection2 == null && collection1!=null))
{
return false;
}

if (ReferenceEquals(collection1, collection2))
{
return true;
}

int collection1Count = collection1.Count();
if (collection1Count != collection2.Count())
{
return false;
}

return collection1Count == 0
|| !AreCollectinDifferent(collection1, collection2);
}

private static bool AreCollectinDifferent(IEnumerable<T> collection1, IEnumerable<T> collection2)
{
int collection1Count;
int collection2Count;

var firstElementCounts = GetElementCounts(collection1, out collection1Count);
var secondElementCounts = GetElementCounts(collection2, out collection2Count);

if (collection1Count != collection2Count)
{
return true;
}

foreach (KeyValuePair<T,int> keyValuePair in firstElementCounts)
{
collection1Count = keyValuePair.Value;
secondElementCounts.TryGetValue(keyValuePair.Key, out collection2Count);

if (collection1Count != collection2Count)
{
return true;
}
}

return false;
}

private static Dictionary<T, int> GetElementCounts(IEnumerable<T> enumerable,
out int nullCount)
{
var dictionary = new Dictionary<T, int>();
nullCount = 0;
int value;

foreach (T element in enumerable)
{
if (element == null)
{
nullCount++;
continue;
}


dictionary.TryGetValue(element, out value);
dictionary[element] = ++value;
}

return dictionary;
}

public int GetHashCode(IEnumerable<T> enumerable)
{
return enumerable
.OrderBy(x => x)
.Aggregate(
11,
(current, val) => current*13 + val.GetHashCode());
}
}

Enjoy!

Comments

  1. 11 si 13 ce reprezinta? :)

    Interesant ca si implementare- altfel, daca timpul m-ar fi presat as fi raspuns la intrebare: foloseste ceva gata facut, precum http://comparenetobjects.codeplex.com/ (l-am folosit in unit teste, si merge brici, exceptand niste situatii destul de particulare)

    ReplyDelete
  2. Am implementat o functie de hash. Ma asteptam ca cineva sa se ia de functie de hash. Nu e cel mai bun algoritm acolo oricum.
    + o bere Tudor pe cand te intorci :D

    ReplyDelete
  3. Imi dau seama ca e o functie de hash, eram curios de ce 13 si nu.. 15.. :)

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP