Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>There's no particular reason why that order was chosen. The chosen order goes from more general to more specific, which I suppose is a reasonably nice property.</p> <p>As for the question "why require an order at all?", it's simply easier on the implementation and testing teams to have a clear, unambiguous order imposed by the language. We could allow the constraints to come in any order, but what does that buy us?</p> <p>The longer I work on languages the more I'm of the opinion that every time you give the user a choice, you give them an opportunity to make a bad choice. A basic design principle of C# is that we tell you when things look wrong and force you to make them right -- which is not a basic design principle of, say, JavaScript. Its basic design principle is "muddle on through and try to do what the user meant". By placing more restrictions on what is correct <em>syntax</em> in C# we can better ensure that the intended <em>semantics</em> are expressed well in the program.</p> <p>For example, if I were designing a C#-like language today there is no way that I would have ambiguous syntaxes like:</p> <pre><code>class C : X , Y </code></pre> <p>or </p> <pre><code>... where T : X, Y </code></pre> <p>Y is clearly intended to be an interface. Is X? We can't tell syntactically whether X was intended to be an interface or a class. Suffice to say this ambiguity greatly complicates things like detecting cycles in base types vs interfaces and so on. It'd be much easier on all concerned if it were more verbose, as it is in VB. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload