3 ms·
Generics being reified in the CLR are entirely biased to C# (and vice versa), which is exactly why they impeded scala.net. They were simply designed for each ot
by seanmcdirmid 7y ago
Generics being reified in the CLR are entirely biased to C# (and vice versa), which is exactly why they impeded scala.net. They were simply designed for each other.
Extensions methods are great, tracking down the methods that you are calling is super easy in an IDE. The ability to abstract over generic type parameters as well as class subtype is very useful.
Default interface implementations have no connection to extension methods, they solve different problems.
Explicit method implementations are great at avoiding name collisions as well as accidental ones. The coercions needed are not hard casts, though C# could do be improved with a soft cast operator.
- pjmlp 7y agoCLR is called Common Language Runtime and not C# Language Runtime. In fact, C++/CLI is the only Microsoft language that has full access to all CLR features, not C#. A language that has a much more expressive OO model than either Java or C#, and requires reiffed generics. IDEs don't work in code review workflows.
- seanmcdirmid 7y agoFor all intensive purposes, the CLR evolves with C# in lockstep. Multi language might have been a goal at one time, but isn’t really anymore. No one really uses C++ CLI. > IDEs don't work in code review workflows. Use or make better tools.
- pjmlp 7y agoYou should come out from your Ivory tower. Thousands of developers use F#, VB.NET, Powershell, C++/CLI every day, and to lesser extent Cobol and Fortran compilers for .NET. C++/CLI support was a must have requirement for .NET Core adoption, not only because of externals, because all .NET UI Frameworks make use of C++/CLI. So much for no one really uses. We use the tools our customers are willing to pay for. Care to provide a link to a code review tool with IDE like capabilities for code navigation?