In Java, it is good practice to use interface types rather than concrete classes in APIs.
Your problem is that you1 are using ArrayList
(probably in lots of places) where you should really be using List
. As a result you created problems for yourself with an unnecessary constraint that the list is an ArrayList
.
This is what your code should look like:
List input = new ArrayList(...);
public void doSomething(List input) {
List inputA = input.subList(0, input.size()/2);
...
}
this.doSomething(input);
1 - Based on your comments, "you" was actually someone else ... who set this problem in an interview question. It is possible that this was actually a trick question, designed to see how you would cope with creating a (real) slice of an ArrayList
that was a assignment compatible with ArrayList
.
Your proposed "solution" to the problem was/is this:
new ArrayList(input.subList(0, input.size()/2))
That works by making a copy of the sublist. It is not a slice in the normal sense. Furthermore, if the sublist is big, then making the copy will be expensive.
If you are constrained by APIs that you cannot change, such that you have to declare inputA
as an ArrayList
, you might be able to implement a custom subclass of ArrayList
in which the subList
method returns a subclass of ArrayList
. However:
- It would be a lot of work to design, implement and test.
- You have now added significant new class to your code base, possibly with dependencies on undocumented aspects (and therefore "subject to change") aspects of the
ArrayList
class.
- You would need to change relevant places in your codebase where you are creating
ArrayList
instances to create instances of your subclass instead.
The "copy the array" solution is more practical ... bearing in mind that these are not true slices.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…