The best explanation you can ask for

When I was looking for a video to explain the C# record, I knew I was in good hands. Always to the point, no big talk around it. Many greetings from Germany

I love your short but very informative videos! You just got a new subscriber!

Brilliant video, that was so concise and informative, thank you.

great explanation! i've struggled with how classes and recs are different, so this really helped a lot.

Amazing explanation and demonstration keep it up!

You have an excellent concise teaching style.

Great explanation, thanks!

I would absolutely love if this encourages people to put a bunch of (related) types into the same file so we don't get a bajilllion files just for simple types.

Sweet. That makes sense. Didn't really see how record was useful, but this makes sense. Thanks!

this was the clearest explanation video I've ever seen in a while. GJ!

Thanks Shawn

First time visitor. Senior dev that just wanted to see some different explanations on the topic in the context on how to best describe it. You explain in a concise and pedagogical way. You do this without all the the Bells and Whistles that usually comes with KZfaq videos. I hesitate to search for explanations in video format because it often comes with too much distraction and ambition. Motivated or not, things I didn't want. This, however, really gets to the point in a straight forward and relaxing manner. Nice!

Good video, and ur voice is so relaxing sir.

Cool video 👌

Thanks this was great.

You should mention how and when a record will be allocated to the heap vs stack as this is important for performance and GC. Also, go into when and how copying of a record instance is a fill/deep copy, meaning no references are reused, and when it is a shallow copy, meaning value types are copied but reference types only have the pointer copied.

Video and audio quality are ridiculously good. Need S Dubs in the highest def possible

helpful👍🔥

Thanks for this! But what's your take on creating DTOs with records instead of with classes?

You didn't really say why we should use records but thanks anyway.

Thanks for doing these insighful coding shorts. I noticed you use a shortcut to run the 'dotnet.exe' -was it a case of just making a copy and naming it 'n.exe' (in the same folder)?

Hi Shawn, could you give a video talking about the "readonly record struct"? The name seems a bit wired, and it is rarely mentioned. What is its application scenario?

First of all, even if i point out a flaw, i really love your shorts, this video helped me alot in finding a simple way to explain this construct to my trainees and junior devs. The flaw im talking about starts at 1:50 of your video. There you are telling that you make a copy of the product by writing this: var product2 = product; But thats not true, you dont make a copy you just assign the pointer to another variable, you copied the pointer, not the object. You can test it by using this Code: var product2 = product; product.Description = "Description of Product"; Console.WriteLine($"Product1: {product.Description}"); Console.WriteLine($"Product2: {product2.Description}"); If i had a Copy, then only the first Console WriteLine should contain the Description string "Description of Product". But both does and thats because those variables actually do point to the same object and for that makes your explaination later with equals a bit weird.

How is that last bool method you wrote a part of the record above? What indicates that?

What I really want to do is make all of my DTOs readonly record struct. But it doesn't work in a number of cases including [AsParameter].

thanks my amercian bro

You can also mutate the record back onto itself e.g. product = product with { Price = 1.99m } I use this in Fluxor where the current state is passed into a reducer method.

how do I convert records into classes and vice versa?

Are you the voice of Lester in GTA5?