C# 11's new operator #Shorts Software Nick Chapsas — 16/10/2022 · 39 Comments Let’s take a look at the new C# 11 operator called the bang-bang operator !! operator C# .net 6 features .NET Core .netcore argument null exception ArgumentNullException bang bang operator bang bang operator c# c# c# 11 chapsas clean code coding core dot net dotNET dotnet 6 elfo Elfocrash net 6 nick chapsas operator shorts software engineering tutorial
different strategies to keep null there anyways. just get rid of nulls and you will not need any of this shits
Can we get a boom, boom operator as well
So much syntactic sugar in c# lately that
I now have type 2 diabetes
It was removed.
Now they just need an operator that also checks for empty/whitespace!
I am not imaginary
Useless feature and it’s making the language harder for any person to just pick up and learn. Yes Java is still too verbose for me but some of these feature aren’t adding that much value. I would like to be able to adopt C# for high perf financial applications
This has now been removed from C# 11, thank god, I am not a fan of it
From a novice viewpoint, C# is getting too congested, there are just too many things to remember, I constantly find myself slipping into "you don't know this, you don't know that" mindset, and cant help but go through the same language syntax books/tutorials again and again just to gain my confidence back.
And what's the point of the name? it looks stupid and its name "bangbang operator" sounds even more stupid..
meanwhile me who is still using .net 4.8
Now that we have a "bang bang" operator, where's the "ugh, augh, I'm dying you idiot" operator?
Hmm wouldn't two question marks be more suitable?
Got shown this short today and wondered if the !! is back… Oh well
"Imaginary viewer", I'm offended, how dare you. I'm very real.
Awesome videos BTW.
It seems like language doesn't going this road. What is the point of this video being around?
I do not like this operator in other language and now it will be in C# 🙁
It is not readable.
i thought they removed this operator
It's a perfect introduction to structuring your code to be designed in a way that it should only pass references around if they are actually pointing to something. The source of a reference should never return a reference to nothing (null) in the first place but hey, ask the guy who invented null references 😀
Another instance of C# nullables being a patch job instead of being designed properly. IMO ‘!’ should have had this behaviour from the get-go instead of being the “null forgiving” operator that would let you send null to a non null arg to begin with
If "!" is the "damnit" operator, presumably, "!!" Is the "Goddamnit" operator.
Imagine having to deal with null pointers
This comment was brought to you by the Haskell gang
Pass me a null argument and I miss the part where that's my problem
I'll have to see the full video to know if it's worth the potential confusion.
Oh FFS. Who asked for this?
Would rather be able to configure a project to automatically throw null exceptions if a null is passed in and it's using nullable reference types. They're doing some goofy shit lately. Look at the proposal they have for lambdas…
I hate this syntax
C# is such a mess 😂
I don't like how bloated c# is.
Wait, is c# now kotlin?
As far as I'm aware, C language was designed to be having as few keywords and operators as possible.
C# is making synonyms after synonyms.
Might as well call it #C at this point.
Would perfectly describe how f#Cking overloaded it has become completely flipping the point of C language family.
C# is pure garbage…
Ahhh yes C# the language with 900 ways to check for nullability…
Reason 4462 why C# is a bad language
Literally took this straight from Kotlin
I don't like c# because it's just so many little things, no real logic, a separate operator for every problem
Unpopular opinion but I think this operator helps keeping things clean and is definitely on the right path to good usage too
looks horroble at first sight but I'm interested to see it in action