this post was submitted on 13 Nov 2024
1733 points (96.1% liked)
Technology
60063 readers
3472 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
.Equals
and==
have different meaning in C#. Decent IDEs will warn you about that (and yes, that excludes Visual Studio, but that always was crap π).I admit, "canonical C#" looks like shit due to a fuckton of legacy stuff. Fortunately, newer patterns solve that rather neatly and that started way back in C# 6 or 7 (with arrow functions / props and inlined
out
s).Tl;dr: check the new features, fiddle with the language yourself. Because hell, with
ref struct
s you can make it behave like quasi-Rust.Equals and == has different meanings? Like === in php or is it javascript π
If you don't see the problem with reassignment/pointer walking, then you are just too used to it to notice that it is total shit, how do you even copy the data from an instance of a class to another... Or are you "not supposed to do that"? If so, okay, but then c# is a 'simple' language, a script language like python or php.
Also when you have a class A, make an instance isn't:
A a;
I mean wtf...
To each their own I guess :-) !