C Sharp

1526 readers

1 users here now

A community about the C# programming language

Getting started

Useful resources

IDEs and code editors

Visual Studio (Windows/Mac)
Rider (Windows/Mac/Linux)
Visual Studio Code (Windows/Mac/Linux)

Tools

Decompilers: ILSpy, dotPeek
Scratchpad: LINQPad
Online playground and IL viewer: SharpLab

Rules

Rule 1: Follow Lemmy rules
Rule 2: Be excellent to each other, no hostility towards users for any reason
Rule 3: No spam of tools/companies/advertisements

Related communities

c/dotnet

founded 1 year ago

MODERATORS

[email protected]

Writing “string.IsNullOrEmpty” using pattern matching and comparing the resulting code (www.tabsoverspaces.com)

submitted 5 months ago by [email protected] to c/[email protected]

4 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 5 months ago (1 children)

The usual convention is to have extension methods behave like regular methods, I.E. don't allow them to accept nulls. When looking at foo.Bar(); it's better if I can just intuit that foo can't be null because you're not supposed to be able to invoke the . operator on null.

Of course, I'm entirely guilty of breaking this rule myself. cough Shoudly cough FluentAssertions cough

[–] [email protected] 2 points 5 months ago* (last edited 5 months ago)

I've always used the Nullable context so typically I'm just using string.IsNullOrEmpty to determine empty strings, I'm already confident null isn't leaking. But your explanation does make sense.

I'm now wondering why I've never just used myStr != ""