Skip to main content

Lambda expression si recursivitatea

Astazi aveam de parcurs o structura arborescenta. Din punct de vedere a implementarii nu era cine stie si aveam doua optiuni:
  • o metoda care se apeleaza recursiv;
  • un while care sa faca cautarea in interiorul la structura pe care o aveam;
Dar am zis sa incerc sa folosesc expressi lambda si iata ce a iesit:
Func<Tree, Tree> searchParent =
currentCategorie =>
!currentCategorie.Parent != null
? currentCategorie
: searchParent(PlainTree.First(parentTree => parentTree == currentTree.Parent));

Sa va spun sincer am renutat la ea, din cauza ca nu era tocmai usor de inteles. Dar conteaza ca se poate, iar daca ne folosim imaginatia putem sa facem unele chestii destul de interesante.
Problema care o vad nu este la modul de implementare, nu este complicat deloc sa folosim doar expresii lambda( daca ne ajutam si de Func,Action si delegates putem sa facem aproape orice). Probleme o sa apara in momentul in care vrem sa facem debug pe un cod care nu este scris de noi. Expresiile lambda nu sunt foarte usor de inteles cand se intind pe mai multe randuri, iar impreuna cu recursivitate o sa le dam batai de cap celor care vin dupa noi. Codul IL generat in spate daca folosim lambda expression o sa fie chiar mai complicat decat daca folosim mecanismul standard.
Iata un exemplu de program care foloseste lambda expression si recursivitatea:
public class Program

{

delegate T SelfApplicable<T>(SelfApplicable<T> self);



static void Main(string[] args)

{

// The Y combinator

SelfApplicable<

Func<Func<Func<int,int>,Func<int,int>>,Func<int,int>>

> Y = y => f => x => f(y(y)(f))(x);



// The fixed point generator

Func<Func<Func<int, int>, Func<int, int>>, Func<int, int>> Fix =

Y(Y);



// The higher order function describing factorial

Func<Func<int,int>,Func<int,int>> F =

fac => x => x == 0 ? 1 : x * fac(x-1);



// The factorial function itself

Func<int,int> factorial = Fix(F);



for (int i = 0; i < 12; i++) {

Console.WriteLine(factorial(i));

}

}

}

Sursa: http://www.lostechies.com/blogs/jimmy_bogard/archive/2007/05/18/fun-with-recursive-lambda-functions.aspx
Eu cred ca as cobora un sfant daca ar trebuii sa fac debug pe codul de mai sus. Nu il poti intelege in 2 secunde, ai nevoie de cateva momente pana intelegi ce se face acolo.
Unde as folosii eu expresiila lambda si recusivitatea? Pe orice fel de grafe, dar nu as incerca sa implementez in expresii lambda tot mecanismul de recursivitate.
Ar fi mai interesant ca avem metode ajutatoare pe noduri, care sa ne ajute sa iteram noduriile fiu de exemplu pe baza unor conditii care le dam prin expresii lambda, iar cand ajungem la nodul dorit sa putem executa o actiun pe baza unui action.
public void ProcessChildrens(Func<Node,bool> condition,Action<Node> action)
{
Childrens.ForEach(node => node.ProcessChildrens(condition, action));

if (condition(this))
{
action(this);
}
}


Concluzie: Chiar daca e mai fancy sa implemetam o functie recursiva intr-o lambda expression, nu recomand acest lucru daca codul este de o complexitate mediu sa ridicata, deoarece o sa fie foarte greu de inteles apoi. Dar exista cazuri cand ne putem folosii de ele.

Comments

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

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

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

Context
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…