Skip to main content

Cum putem sa verificam tipul unei variabile intr-un SWITCH

Sunt momente cand avem nevoie de a face anumite actiuni in functie de tipul variabilei. Din pacate SWITCH-ul nu ne permite acest lucru in mod direct si suntem nevoiți sa apelam la IF..ELSE.
if (item is int)
{...}
else if (item is string)
{...}
else if (item is DateTime)
{...}
else if (item is ...)
Codul pe care il obtinem nu este foarte lizibil. Daca totusi am vrea sa folosim SWITCH am fi nevoiti sa lucram cu string-uri obtinand ceva asemanator cu:
swtich( v.GetType().Name)
{
case typeof(int).Name:
...
break;
case typeof(DateTime).Name:
...
break;
...
}
Parca e mai bine decat codul precedent, dar ceea ce nu e tocmai bine este ca lucram cu string-uri. O solutie la aceasta problema este sa folosim TypeCode. Acest enum contine toate tipurile built-in din .NET.
switch( Type.GetTypeCode(v.GetType)))
{
case TypeCode.Int32:
...
break;
case TypeCode.DateTime:
...
break;
...
}
In cazul in care lucram doar cu tipurile built-in din .NET totul este perfect. Ceea ce imi place la TypeCode este ca are valori precum "Empty" sau "DBNull". Dar ce ne facem daca lucram cu vectori, cu liste generice sau cu entități proprii. In acest caz TypeCode nu mai poate fi folosit. Pentru acest caz eu am gasit doua rezolvari. O solutie este sa ne folosim de un dicționar de forma:
Dictionary<Type, int>
sau
Dictionary<Type, [CustomEnum]>
In cazul acesta am putea sa adaugam la initializarea dictionarului toate tipurile cu care lucram, iar apoi sa scriem un switch asemanator cu acesta:
swtich( types[v.GetType()])     // types - este o instanta a dictionarului in care avem toate tipurile cu care lucram.
{
case 0: //sau case CustomEnum.Int32
...
break;
case 1: //sau case CustomEnum.DateTime
...
break;
...
}
Urmatoarea solutie pe care o propun este sa ne definim o clasa CustomSwitch iar pentru fiecare case in parte sa ne definim actiunea dorita. Putem sa ne definim modelul si intr-un mod fluent, a.i. la final sa putem aveam ceva asemanator cu:
var customSwitch = new CustomSwitch(v)
.Case<int>( x => ...actiune... );
.Case<DateTime>( x => ...actiune... );
Mai jos puteti sa gasiti implemenentarea pentru CustomSwitch:
public class CustomSwitch
{
public CustomSwitch(Object obj)
{
Obj = obj;
}

public Object Obj { get; set; }
}
public static class CustomSwitchExtensions
{
public static CustomSwitch Case<T>( this CustomSwitch cs,Action<T> action)
where T : class
{
var obj = s.Obj as T;
if (obj != null)
{
action(obj);
return null;
}
}
}
La aceasta implementare s-ar mai putea adauga si un flag care sa permita un mecanism de fall through si prin celelalte case-uri. Din cele doua variante propuse as alege a doua varianta doar in cazul in care as avea nevoie si de un mecanism de fall through. De exemplu in cazul in care as avea nevoie sa execut doua case-uri pentru un obiect( ex. in cazul in care implementateaza interfata IA o actiune, si pentru interfata IB o alta actiune).

Comments

  1. :) Daca faci switch pe type ai o problema mult mai mare decat "cum sa faci". Think polymorphism :)

    ReplyDelete

Post a Comment

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...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...