Computer scienceProgramming languagesJavaCode organizationGeneric programmingGenerics internals

Type Erasure

Universal Integer

Report a typo

Your colleagues came to you with an idea to create a UniversalInteger class. The objects of the class can be compared with themselves and objects of any other integer classes: Byte, Integer, and Long. The code snippet that illustrates their idea is:

class UniversalInteger implements Comparable<UniversalInteger>, 
                                  Comparable<Byte>, 
                                  Comparable<Integer>, 
                                  Comparable<Long> {

    // a body
}

What would you say to them?

Select one option from the list

This wouldn't work because there is no natural order for integers of different types

The idea is great: we often do not care of exact type during comparison

This wouldn't work since class can't have multiple methods with same signatures

This wouldn't work: this code tries to implement multiple interfaces with same erasure

This wouldn't work since erasure for Byte, Integer and Long is Number

___

Create a free account to access the full topic