Skip to main content

Care este cea mai rapida metoda pentru a obtine index-ul unui element din IEnumerable

De cate ori nu v-ati lovit de acest caz? Sa aveti un obiect de tip enumerable si sa fim nevoiti sa obtineti indexul unui element.
Exista mai multe metode pentru a rezolva aceasta problema, cea mai simpla din ele este:
obj.ToList().FindIndex( x => x =="Blog" )
Pentru cazul in care am cautat elementul care are valoarea "Blog".
Daca ne punem problema vitezei putem sa scriem noi o metoda popie:
public static int FindIndex<T>(this IEnumerable<T> elemente, Predicate<T> conditie)
int index = 0;
foreach (var item in elemente)
if (conditie(item))
return index;
return -1;
Prima optiune ne sperie putin din cauta la ToList(). Ne punem problema performantei, am prefera parca sa nu folosim ToList() si sa mergem pe metoda scrisa de noi.
elemente.Select((item, index) => new { item, index })
.Where(p => p.item == "Blog")
.Select(p => p.index + 1)
.FirstOrDefault() - 1;
Ce am facut mai sus? Nimic complicat, am obtinut toate elementele din enumeratie sub forma (element, index). Daca nu stiati Select-ul ne permite acest lucru, ne poate fi de ajutor aceasta metoda in multe alte situatii. Apoi am selectat doar elementele care respecta conditia, iar apoi am selectat index-ul la acest element. FistOrDefault ne garanteaza ca acest algoritm se va oprii dupa ce a gasit primul element care indeplineste conditia data. M-am folosit de +1 si -1 la Select si la FirstOrDefault pentru a putea avea rezultatul -1 cand nu se gaseste nici un element in enumeratie ce sa indeplineasca conditia data.
Mai exista si alte mecanisme, folosind TakeWhile.
Problema nu este neaparat cum, ci care este mai optim mecanism.
Desii e greu de crezut cel mai rapid mecanism este ToList().FistIndex(). Se pare ca nu intoadeauna un cod scris de mana este mai rapid ca si un API default oferit de catre .NET, chiar daca vorbim de LINQ.


  1. Interesant - ai facut niste masuratori ca sa vezi cu cat e mai rapida metoda ce foloseste LINQ/Select ?
    (la prima metoda, nu mi-e prea clar de ce era nevoie sa se foloseasca ToList())

  2. Problema e ca query-ul scris cu LINQ e gresit. Punand clauza Select((item, index) => new { item, index }) prima, am invalidat tot lazy-loading-ul care il ofera LINQ.
    Corect ar fi:
    elemente.Where(p => p.item == "Blog")
    .Select((item, index) => new { item, index })


Post a Comment

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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 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.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…