Skip to main content

Where clause

Mai mult ca sigur cu toții am folosit clauza where.
Pe scurt, where este folosit când trebuie sa adaugăm o constrângere la un tip generic specificat la o clasa sau la o metoda.
public class Car<TType>
where TType : ICarModel
{}
In exemplul de mai sus o sa putem folosii tipuri generice TType doar dacă implementează interfața ICarModel. In cazul in care vrem sa specificam ca tipul generic sa fie neaparat o clasa este nevoie sa ne folosim si de cuvantul rezervat class:
public class Car<TType>
where TType : ICarModel, class
{}
In cazul acesta, TType trebuie sa fie obligatoriu sa fie o clasa (nu va putea sa fie o structura de exemplu). Pentru structuri trebuie sa folosim cuvantul rezervat struct:
public class Car<TType>
where TType : struct
{}
Dar dacă vrem sa face new de un obiect de tip generic? In cazul aceasta trebuie sa specificam ca are un constructor default în clasau de where. Din păcate doar constructorul default fără parametri se poate specifica. In restul cazurilor o sa aveți nevoie de un factory sau de reflection pentru a crea noi instante din interiorul clasei Car.
public class Car<TType>
where TType : new()
{}
Gata cu introducerea, sa va zic ce vroiam de fapt. Cand avem 2 clause de where sintaxa este destul de ciudata, trebuie sa specificam de doua ori where.
public class Car<TType,TFormat>
where TType : new()
where TFormat : struct
{}
Mi se pare umpic mai ciudat ca cele doua where-uri nu sunt despartite prin virgula sau alt caracter (cuvînt rezervat).
Voua cum vi se pare sintaxa?

Comments

  1. Probabil ca sa simplifice un pic parser-ul: daca permiteau ceva de genul:
    where TType: IComparable, IEnumerable, TFormat : struct
    compiler-ul ar trebui sa se uite in avand ca sa isi dea seama ca TFormat nu e un tip de baza pentru TType, ci un tip generic..

    ReplyDelete
  2. Dar dacă vreau sa specific încă o clasa de "where" nu mai este nevoie sa pun nici o virgula sau un alt caracter special. Mi s-a părut destul de interesant, pana ieri nici nu am observat lipsa acestui semn.

    ReplyDelete

Post a Comment

Popular posts from this blog

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

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

[Post Event] Azure AI Connect, March 2025

On March 13th, I had the opportunity to speak at Azure AI Connect about modern AI architectures.  My session focused on the importance of modernizing cloud systems to efficiently handle the increasing payload generated by AI.