Skip to main content

Structure and "Cannot modify the return value of XXX because it is not a variable" error

In ziua de azi aproape toata lumea foloseste clase. Cand aude cineva de struct, se uita la tine ciudat, de parca ai venit din evul mediu. In unele cazuri o structura este o optiune mult mai buna decat o clasa, dar nu despre asta o sa discutam astazi. O sa discutam putin despre o eroare pe care multa lume o primeste cand lucreaza cu struct.
Cannot modify the return value of XXX because it is not a variable
Cod sursa:
struct Foo
{
public int Value { get; set; }
}

class FooContainer
{
public FooContainer()
{
Foo = new Foo() {Value = 1};
}
public Foo Foo { get; private set; }
}
...
FooContainer fooContainer=new FooContainer();
fooContainer.Foo.Value = 2; // !!!
Cauza la aceasta eroare nu este limbajul, Visual Studio sau orice alt dezvoltator care a lucrat la proiect. Este vina celui care vrea schimbe valoarea unei date dintr-o structura.
O structura poate sa contina constante, field-uri, propietati, operatori, evenimente, index-uri etc. Aceasta se poate folosii 'oarecum' ca si o clasa, dar este un VALUE TYPE pana la moarte.
Ce inseamna asta? Nu se poate sa mosteneasca o alta structura, nu poate sa fie derivata, nu poate sa contina valoarea NULL etc. Pentru o definitie completa va rog sa va uitati la urmatoarea adresa http://msdn.microsoft.com/en-us/library/s1ax56ch%28v=vs.71%29.aspx
Ce ne intereseaza pe noi cel mai mult este ca structurile sunt "IMUTABILE" din anumite puncte de vedere - odata ce au fost create, starea lor interna nu poate sa fie schimbata. Nici o valoare din interiorul unei structuri nu poate sa fie modificata. De fapt, ce se intampla in spate cand facem o noua "referinta" la structura, este sa se creeze o noua copie a acesteia. Cand referim o alta structura se copiaza valoarea s-a si nu referinta.
Din aceasta cauza orice modificare pe care noi o facem la structura, se va face pe copia ei si nu pe structura insasi. Daca dorim sa facem acest lucru atunci este nevoie sa inlocuim toata structura, creand una noua.
Din aceasta cauza un field se poate initializa o singura data, in momentul in care construim structura. Orice modificare a unui field dupa acest moment nu o sa mai poata sa fie facuta.
Nu trebuie sa uitam ca nu are rost sa ne definim un contructur pentru o structura - care sa itializeze campurile cu valoare defapt, deoarece by default o sa avem mereu unul care va face acest lucru(pentru fiecare camp in parte).
Enjoy!

Comments

  1. //...
    FooContainer fooContainer = new FooContainer();
    Foo foo = fooContainer.Foo;
    foo.Value = 2;
    /// atentie doar ce faci cu foo mai departe, deoarece fooContainer.Foo (originalul) nu va reflecta modificarea ta - Foo fiind un value type
    /// restrictia de a modifica un value type returnat de o proprietate sau metoda vine tocmai din faptul ca iti returneaza o copie de care trebuie sa ai grija explicit atunci cand o modifici.
    /// Imutabilitatea nu are legatura cu asta iar value type-urile nu sunt imutabile prin definitie. exemplul de mai sus o demonstreaza.

    BTW, foarte fain topicul!

    ReplyDelete
  2. Din cauza asta am pus cu ghilimele imutabil. In exemplul dat mai sus se comporta din unele puncte de vedere ca un obiect imutabil.

    ReplyDelete
  3. Cauza e si limbajul oarecum, fiindca struct in C# e alt animal decat in C++ (unde e prea putin diferit fata de un class )- cine a invatat mai intai C++ nu se asteapta la multe din "surprizele" din C# (care au logica lor, da' ...) - probabil mai tii minte discutia: http://ronua.ro/CS/forums/t/8066.aspx :)

    ReplyDelete

Post a Comment

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

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP