Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Java generics, how to work around type erasure?

Post

Java generics, how to work around type erasure?

+4
−0

This code doesn't compile:

package tryNcry;

public class ExampleClass<S extends SomeClass> {

	S[] createArray(int n) {
		return new S[n]; // obvious compile time ERROR here: 
                                 // Cannot create a generic array of S
	}
}

The reason for this is obvious: due to type erasure, at runtime there is no way for the JRE to know what S would have been, and so no way to create an array for type S.

Everything would be fine (if tedious) if there was any instance of S, using reflection.

How can I solve this?

History

1 comment thread

Generics and arrays don’t mix well, for precisely the reasons you’ve encountered. The best solution ... (1 comment)
Generics and arrays don’t mix well, for precisely the reasons you’ve encountered. The best solution ...
VGR‭ wrote 6 months ago

Generics and arrays don’t mix well, for precisely the reasons you’ve encountered. The best solution by far is to avoid arrays and use a List instead:

List<S> createList(int n) {
        List<S> list = new ArrayList<>(n);
        list.addAll(Collections.nCopies(n, null));
        return list;
}