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

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

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