PropertyChanged VS csharplang

Add [AddINotifyPropertyChangedInterface] attribute to the class for change notification.

All the weaving libraries (also called weavers or addin) using Fody need to have the .Fody suffix, so it's quite easy to recognize them. As an example, if you ever had to implement INotifyPropertyChanged manually in a class with dozens of properties you would probably welcome weaving (and Fody) with open arms. By creating all the plumbing code directly in IL, libraries like PropertyChanged.Fody allows to inject the necessary notification code without the need to modify anything in the original source code.

You can rewrite auto-props (as used this this lib https://github.com/Fody/PropertyChanged) with Fody.

If you're not familiar with Fody and specifically the PropertyChanged weaver, I highly recommend checking it out: https://github.com/Fody/PropertyChanged

Now the ugly part - you need to implement INotifyPropertyChanged. It can be done either manually, or automated with this or this

https://github.com/Fody/PropertyChanged and Android background makes WPF pretty easy. At least the surface level stuff.

If you really don't want to deal with it ever again, just add this Fody - PropertyChanged NuGet package. Any class that inherits from INotifyPropertyChanged will be updated at compile time to inject in the boilerplate code for handling the property change and you never even need to think about it again. All you need to do is just add plain old properties. The only downside that some people see is that it is not immediately transparent as the change notification code is injected in during compile and is not in source code.

And GitHub is the place where employees of billion dollar companies pester unpaid maintainers because they won’t support a 12 year old version of .NET

https://github.com/Fody/PropertyChanged/issues/270#issuecomm...

If you need more info, check the docs https://github.com/Fody/PropertyChanged

Certain parts of Microsoft Learn are permissive, for example the .NET BCL documentation is Creative Commons Attribution: https://github.com/dotnet/dotnet-api-docs as is ASP.NET Core: https://github.com/dotnet/AspNetCore.Docs (a good hint if documentation is permissively licensed and on GitHub is if there's an edit button at the top.)

The C# language specification is unfortunately a bit fuzzier: https://github.com/dotnet/csharplang/discussions/4855

The updated unified C# language specification is CC, but it's still catching up to modern C#: https://github.com/dotnet/csharpstandard

No OP, but for example you still see the C# folks still struggling to add discriminated unions to the language because of complex interactions due to its too many features[1]. Virtual threads are easier to use than async/await is another example.

[1] https://github.com/dotnet/csharplang/issues/113

For example, C# had a research fork called Spec# that had compile-time support for contracts, with keywords such as requires (for arguments) and ensures (for return values), all the way back in 2004. While still being discussed, it doesn't seem to be shipping any time soon.

Hi there. I'm the language designer who created the 'Collection Expression' design/specification: https://github.com/dotnet/csharplang/issues/5354

You can see the entire history of the proposal there. To answer you specific question, we went with `..` because that's what the language already uses for the complimentary 'pattern matching deconstruction' form for collection patterns.

In other words, you can already say this today:

    if (x is [var start, .. var middle, .. var end]) { ... }

You must specify concrete type.

There was a plan to have "natural type" so "var list = [1,2,3]" would be of type "List" but it was postponed to C# 13 (https://github.com/dotnet/csharplang/issues/5354#issuecommen...)

While C# currently lacks direct support for this kind of functionality, there's a glimmer of hope with an active proposal under discussion that aims to bring this feature to the language. This potential addition promises a future where C# can natively offer similar robust type narrowing.

Given few people anticipated ValueTuple and C# adding a more direct tuple syntax, I feel like it is only a matter of time before C# adds discriminated unions.

(There are multiple proposals tracking the idea. This seems the most comprehensive and "central": https://github.com/dotnet/csharplang/issues/7016)

I always liked list abbreviations in python, but I absolutely love Linq. I believe there is a feature proposal for C# 12, which makes collection initialization better imo.