| restricted | https://www.maxisoft.org |
| pronunciation | /mäk′sē/ /tē/ /bē/ |
| nationality | Not-a-german |
| countries visited non-professional for at least 7 days | 90+ |
One thing that always bugs me is that I haven't found yet a way to make static code analysis of nullable ref types work over inheritance boundaries - is there already a way available in #dotnet #csharp to solve this issue in a clean way with attributes?
Top 3 #dotnet conf must-watch videos:
1) https://www.youtube.com/watch?v=aLQpnpSxosg
Three of the main issues with C# are:
- Nullability
- Immutability
- Disposable objects
Now for all three there are imperfect solutions available, but obviously with a decades long legacy there were limits how far those implementations could go.
A good example is foreach - using a IEnumerable<> will most likely result in a costly try-finally block even when no disposing is needed. Sadly we got no IDisposableEnumerator from the start but the generic approach was chosen.
You can see more info about the state of extension everything here:
https://www.youtube/watch?v=O3hx6oPWzX8&t=1060
BTW I think it's very bad practice to rename framework types for one simple reason: It makes the code unreadable to everyone but you, even with best intentions in mind. So you might make yourself more enemies than friends going down this road.
