> if (customer?.Profile is not null) >{ > // Null-coalescing (??) > customer.Pro... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		billmcneale 5 months ago \| parent \| context \| favorite \| on: What's New in C# 14: Null-Conditional Assignments > if (customer?.Profile is not null) >{ > // Null-coalescing (??) > customer.Profile.Avatar = request.Avatar ?? "./default-avatar.jpg"; >} Isn't this over engineered? Why not allow the assignment but do nothing if any of the intermediate objects is null (that's how Kotlin does it).

LelouBil 5 months ago [–]

That's what's new in c#14, it allows you to do

    customer?.Profile?.Avatar = "thing"

And will do nothing if the left hand side is null (not throw a null reference exception anymore)

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact