title: Use cases of [ordered], the new PowerShell 3.0 feature
body: <p>PowerShell 3.0 CTP1 introduces a new feature <code>[ordered]</code> which is somewhat a shortcut for <code>OrderedDictionary</code>. I cannot imagine practical use cases of it. Why is this feature really useful? Can somebody provide some useful examples?</p>
  
  <p>Example: this is, IMHO, rather demo case than practical:</p>
  
  <pre><code>$a = [ordered]@{a=1;b=2;d=3;c=4}
  </code></pre>
  
  <p>(I do not mind if it is still useful, then I am just looking for other useful cases).</p>
  
  <p>I am not looking for use cases of <code>OrderedDictionary</code>, it is useful, indeed. But we can use it directly in v2.0 (and I do a lot). I am trying to understand why is this new feature <code>[ordered]</code> needed in addition.</p>
  
  <hr>
  
  <h2>Collected use cases from answers:</h2>
  
  <pre><code>$hash = [ordered]@{}
  </code></pre>
  
  <p>is shorter than</p>
  
  <pre><code>$hash = New-Object System.Collections.Specialized.OrderedDictionary
  </code></pre>
  
  <p>N.B. <code>ordered</code> is not a real shortcut for the type. <code>New-Object ordered</code> does not work.</p>
  
  <p>N.B. 2: But this is still a good shortcut because (I think, cannot try) it creates typical for PowerShell case insensitive dictionary. The equivalent command in v2.0 is too long, indeed:</p>
  
  <pre><code>New-Object System.Collections.Specialized.OrderedDictionary]([System.StringComparer]::OrdinalIgnoreCase)
  </code></pre>