Skip to main content

Ordonare in sens invers - generic

Era nevoie sa implementez un mecanism de ordonare. Deoarece existau mai multe tipuri de ordonare pe acelasi obiect, am ales sa folosesc IComparer.
IComparer este un mecanism de comparare extern. Implementarea functiei care face compararea nu este in interiorul obiectului, asa cum este in cazul IComparable. Se foloseste de obicei cand modul in care se face comparatie nu este naturala.
Cand se implementeaza interfata IComparer, este nevoie sa implementam metoda int Compare(T obj1,T obj2), care returneaza o valorea
  • pozitiva daca obj1 > obj2;
  • negativa daca obj1 <>
  • zero daca obj1 = obj2;
Pana aici nu apare nici o problema. Dar daca avem nevoie sa putem face si o ordonare inversa( reverse), apar probleme. Nu neaparat la modul de implementare, putem foarte usor sa ne folosim de operatorul de negare !, ci la modul in care facem implementarea. Am cautat un mecanism de ordonare in sens invers, care sa fie cat mai generic.
Solutia pe care o propun este urmatoarea:
public class ComparerReverse<T>: IComparer<T>
where T: class
{
//Stocam implementarea deja existenta.
private readonly IComparer<T> _comparer;

public ComparerReverse(IComparer<T> comparer)
{
_comparer = comparer;
}

public int Compare(T obj1,T obj2)
{
//Apelam Compare de la implementarea de baza, cu cei doi parametri inversati.
return _comparer.Compare(obj2,obj1);
}
}
Prin solutia propusa nu mai este nevoie sa folosim operatorul de negare ! si putem sa folosim aceiasi apelare pentru ambele sensuri de ordonare:
...
IComparer<T> comparerUsa=crescator
?new UsaComparare()
:new ComparerReverse(new UsaComparare());
...
Urmatorul pas este sa cream un extension method care sa faca ordonarea in sens invers:
public static class ComparerReverseExtension
{
public static IComparer<T> Reverse<T>(this IComparer<T> comparer)
{
return new ComparerReverse<T>(comparer);
}
}
Folosind acest extension method putem sa inversam modul in care se face comparatia apeland Reverse() direct la IComparer pe care vrem sa il folosim pentru a face ordonarea in sens invers.

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...