Databases
StackOverflow2013
Postsdbo
POWhen should or shouldn't I be using generic type constraints?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhen should or shouldn't I be using generic type constraints?
    primarykey
    data
    text
    <p>I've got a base class:</p> <pre><code>public abstract class StuffBase { public abstract void DoSomething(); } </code></pre> <p>And two derived classes</p> <pre><code>public class Stuff1 : StuffBase { public void DoSomething() { Console.WriteLine("Stuff 1 did something cool!"); } public Stuff1() { Console.WriteLine("New stuff 1 reporting for duty!"); } } public class Stuff2 : StuffBase { public void DoSomething() { Console.WriteLine("Stuff 2 did something cool!"); } public Stuff1() { Console.WriteLine("New stuff 2 reporting for duty!"); } } </code></pre> <p>Okay, now say I've got a list of items:</p> <pre><code>var items = new List&lt;StuffBase&gt;(); items.Add(new Stuff1()); items.Add(new Stuff2()); </code></pre> <p>and I want them all to call their DoSomething() method. I could expect to just iterate the list and call their DoSomething() method, so let's say I've got a method to do that called AllDoSomething() that just iterates over the list and does the job:</p> <pre><code>public static void AllDoSomething(List&lt;StuffBase&gt; items) { items.ForEach(i =&gt; i.DoSomething()); } </code></pre> <p>What is the practical difference of the following method?</p> <pre><code>public static void AllDoSomething&lt;T&gt;(List&lt;T&gt; items) where T: StuffBase { items.ForEach(i =&gt; i.DoSomething()); } </code></pre> <p>Both methods appear in real terms, although being syntactically different, to be doing the same thing.</p> <p>Are they just different ways of doing the same thing? I understand generics and type constraints but can't see why I would use one way over the other in this instance.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBenAlabaster
    1. USBenAlabaster
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhen should or shouldn't I be using generic type constraints?
      1. USanishMarokey
      1. VTFavorite
    2. VO
      singulars
      1. POWhen should or shouldn't I be using generic type constraints?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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