Databases
StackOverflow2013
Postsdbo
POJava collections covariance problem
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJava collections covariance problem
    primarykey
    data
    text
    <p>Lets say we have a program which contains such classes:</p> <pre><code>public interface AbstractItem { } public SharpItem implements AbstractItem { } public BluntItem implements AbstractItem { } public interface AbstractToolbox { //well the problem starts here... public List&lt;AbstractItem&gt; getItems(); } public ExpensiveToolbox implements AbstractToolbox { private List&lt;SharpItem&gt; items = new ArrayList()&lt;SharpItems&gt;; public List&lt;SharpItem&gt; getItems() { return this.items; } } public CheapTooblox implements AbstractToolbox { private List&lt;BluntItem&gt; items = new ArrayList()&lt;BluntItem&gt;; public List&lt;BluntItem&gt; getItems() { return this.items; } } </code></pre> <p>Easy, right? Well lets say we now want to make a method like this (in some random class):</p> <pre><code>public void doImportantStuff(AbstractToolbox toolbox) { //important stuff! //this obviously won't work List&lt;AbstractToolbox&gt; items = toolbox.getItems(); //do some stuffwith all items } </code></pre> <p>Now the problem is that in Java collections with generics aren't covariant (hope that's the term I'm looking for) and I can't assign an <code>ArrayList&lt;ExpensiveToolbox&gt;</code> to a <code>List&lt;AbstractToolbox&gt;</code>. The only solution I can see here is to duplicate the code and do a version for each type, but that would obviously suck (what if we had more classes implementing AbstractToolbox with different lists?). Oh obviously the second solution would be to drop the generics and make a normal List, but is it a good practice?</p> <p>Are there any design pattern/practices to tackle such problems?</p> <p>@Edit: ok so I might not be precise enough. I want all the classes which extend AbstractToolbox to have a List of certain classes which extend AbstractItem and then I want a method that will take an AbstractToolbox as a parameter and do something on the items in its list (using the classes that would be defined in AbstractItem so all the items of every possible list would actually have them).</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMateusz Dymczyk
    1. USMateusz Dymczyk
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    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. POJava collections covariance problem
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POJava collections covariance problem
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POJava collections covariance problem
      1. This table or related slice is empty.
      1. VTDownMod
    1. COTo clarify, wouldn't you want your doImportantStuff to have: List<AbstractItem> items = toolbox.getIems();
      singulars
      1. POJava collections covariance problem
      1. USMikeTheReader
    2. COWhat do you mean, "Easy, right?" Your first section doesn't compile, and shouldn't!
      singulars
      1. POJava collections covariance problem
      1. USMark Peters
    3. COWell I figured it would be easy for SO. I mean obviously *I* am having problems with it ;)
      singulars
      1. POJava collections covariance problem
      1. USMateusz Dymczyk
 

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