[OT] Sharp Regrets: Top 10 Worst C# Features

Walter Bright via Digitalmars-d digitalmars-d at puremagic.com
Thu Aug 20 14:14:52 PDT 2015


On 8/19/2015 1:47 AM, Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= 
<ola.fosheim.grostad+dlang at gmail.com> wrote:
> I see your point, but it isn't so clear cut. When you are doing a high level
> APIs, like an ORM you might want to enforce having a field on the left and a
> number on the right and return a query building type. So you can type
> "db.query(ClassA.birth < somedate)"

That's exactly the kind of thing D's operator overloading is designed to discourage.

>> #1: D doesn't suffer from this, thanks to classes being reference types by
>> design.
>
> I think that is the wrong argument, because surely D lifted the struct/class
> dichotomy off C#?

Surely you're wrong. I originally proposed that to Bjarne back in the 1980's. It 
was in D's earliest proposals before Microsoft ever released any info on C#.



More information about the Digitalmars-d mailing list