Restricting the Object Type for the get method in a Java HashMap [duplicate]What are the reasons why Map.get(Object key) is not (fully) genericWhy aren't Java Collections remove methods generic?Does a finally block always get executed in Java?Fastest way to determine if an integer's square root is an integerA Java collection of value pairs? (tuples?)How to get an enum value from a string value in Java?Java Hashmap: How to get key from value?get string value from HashMap depending on key nameHow to update a value, given a key in a java hashmap?java.lang.OutOfMemoryError: GC overhead limit exceededRestrict HashMap to accept a particular string keyWhy does Map.of not allow null keys and values?

How exactly does Hawking radiation decrease the mass of black holes?

Which big number is bigger?

Does a large simulator bay have standard public address announcements?

Why didn't the Space Shuttle bounce back into space as many times as possible so as to lose a lot of kinetic energy up there?

How does Captain America channel this power?

Can SQL Server create collisions in system generated constraint names?

Minor Revision with suggestion of an alternative proof by reviewer

Two field separators (colon and space) in awk

"Whatever a Russian does, they end up making the Kalashnikov gun"? Are there any similar proverbs in English?

Alignment of various blocks in tikz

How can the Githyanki Supreme Commander move while insubstantial?

Why did C use the -> operator instead of reusing the . operator?

How to pronounce 'c++' in Spanish

Map of water taps to fill bottles

Why was the Spitfire's elliptical wing almost uncopied by other aircraft of World War 2?

Is Diceware more secure than a long passphrase?

What term is being referred to with "reflected-sound-of-underground-spirits"?

How to have a sharp product image?

How come there are so many candidates for the 2020 Democratic party presidential nomination?

Why did some of my point & shoot film photos come back with one third light white or orange?

Is there really no use for MD5 anymore?

Coordinate my way to the name of the (video) game

Pre-plastic human skin alternative

How do I reattach a shelf to the wall when it ripped out of the wall?



Restricting the Object Type for the get method in a Java HashMap [duplicate]


What are the reasons why Map.get(Object key) is not (fully) genericWhy aren't Java Collections remove methods generic?Does a finally block always get executed in Java?Fastest way to determine if an integer's square root is an integerA Java collection of value pairs? (tuples?)How to get an enum value from a string value in Java?Java Hashmap: How to get key from value?get string value from HashMap depending on key nameHow to update a value, given a key in a java hashmap?java.lang.OutOfMemoryError: GC overhead limit exceededRestrict HashMap to accept a particular string keyWhy does Map.of not allow null keys and values?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








11
















This question already has an answer here:



  • What are the reasons why Map.get(Object key) is not (fully) generic

    11 answers



I have instantiated my HashMap like this:



Map<String, Integer> myHashMap = new HashMap<String, Integer>();


The datatype of the Key is String, so when I try to insert a new key-value pair in the map keeping the Key as Integer, it throws an error.



myHashMap.put(1L, "value");


That means in the put method they have restricted the datatype of the Key. But while fetching the value from the map using the get method it is not checking for the datatype of the Key. So if I write something like this, it doesn't give a compilation error.



myHashMap.get(1L);


I checked the get method in the Java Map interface and its parameter type is Object, so that's why it is allowing any Object as the put method argument.



V get(Object key)


Is there a way I can restrict the datatype which I pass as an argument in the get method?



The argument that I pass should have the same datatype as the datatype of the Key which I use while instantiating my hashmap.










share|improve this question















marked as duplicate by Roddy of the Frozen Peas, KevinO, Community Apr 22 at 19:05


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.













  • 1





    No. But good IDEs will warn you when doing that. And you can encapsulate the map into your own class.

    – JB Nizet
    Apr 22 at 7:16











  • In other languages you could create extension method, like getTyped.... In Java you can do this with static method, so your call will be getTyped(map, key). Ugly, but works.

    – dyukha
    Apr 22 at 7:22












  • I have considered the option of creating a wrapper method over the get method, something like this: Integer getMapValue(Map map, String Key) return map.get(key) And call this method instead of the get method, but I wanted to know if Java provides any such restricting feature of not?

    – Rito
    Apr 22 at 7:30











  • You can add an implementation of a get(K key) method, but It seems like an unnecessary effort. The return value for a mismatching key (type-wise) will be null, as expected. So the Map will conform to its API.

    – Rann Lifshitz
    Apr 22 at 7:37

















11
















This question already has an answer here:



  • What are the reasons why Map.get(Object key) is not (fully) generic

    11 answers



I have instantiated my HashMap like this:



Map<String, Integer> myHashMap = new HashMap<String, Integer>();


The datatype of the Key is String, so when I try to insert a new key-value pair in the map keeping the Key as Integer, it throws an error.



myHashMap.put(1L, "value");


That means in the put method they have restricted the datatype of the Key. But while fetching the value from the map using the get method it is not checking for the datatype of the Key. So if I write something like this, it doesn't give a compilation error.



myHashMap.get(1L);


I checked the get method in the Java Map interface and its parameter type is Object, so that's why it is allowing any Object as the put method argument.



V get(Object key)


Is there a way I can restrict the datatype which I pass as an argument in the get method?



The argument that I pass should have the same datatype as the datatype of the Key which I use while instantiating my hashmap.










share|improve this question















marked as duplicate by Roddy of the Frozen Peas, KevinO, Community Apr 22 at 19:05


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.













  • 1





    No. But good IDEs will warn you when doing that. And you can encapsulate the map into your own class.

    – JB Nizet
    Apr 22 at 7:16











  • In other languages you could create extension method, like getTyped.... In Java you can do this with static method, so your call will be getTyped(map, key). Ugly, but works.

    – dyukha
    Apr 22 at 7:22












  • I have considered the option of creating a wrapper method over the get method, something like this: Integer getMapValue(Map map, String Key) return map.get(key) And call this method instead of the get method, but I wanted to know if Java provides any such restricting feature of not?

    – Rito
    Apr 22 at 7:30











  • You can add an implementation of a get(K key) method, but It seems like an unnecessary effort. The return value for a mismatching key (type-wise) will be null, as expected. So the Map will conform to its API.

    – Rann Lifshitz
    Apr 22 at 7:37













11












11








11


2







This question already has an answer here:



  • What are the reasons why Map.get(Object key) is not (fully) generic

    11 answers



I have instantiated my HashMap like this:



Map<String, Integer> myHashMap = new HashMap<String, Integer>();


The datatype of the Key is String, so when I try to insert a new key-value pair in the map keeping the Key as Integer, it throws an error.



myHashMap.put(1L, "value");


That means in the put method they have restricted the datatype of the Key. But while fetching the value from the map using the get method it is not checking for the datatype of the Key. So if I write something like this, it doesn't give a compilation error.



myHashMap.get(1L);


I checked the get method in the Java Map interface and its parameter type is Object, so that's why it is allowing any Object as the put method argument.



V get(Object key)


Is there a way I can restrict the datatype which I pass as an argument in the get method?



The argument that I pass should have the same datatype as the datatype of the Key which I use while instantiating my hashmap.










share|improve this question

















This question already has an answer here:



  • What are the reasons why Map.get(Object key) is not (fully) generic

    11 answers



I have instantiated my HashMap like this:



Map<String, Integer> myHashMap = new HashMap<String, Integer>();


The datatype of the Key is String, so when I try to insert a new key-value pair in the map keeping the Key as Integer, it throws an error.



myHashMap.put(1L, "value");


That means in the put method they have restricted the datatype of the Key. But while fetching the value from the map using the get method it is not checking for the datatype of the Key. So if I write something like this, it doesn't give a compilation error.



myHashMap.get(1L);


I checked the get method in the Java Map interface and its parameter type is Object, so that's why it is allowing any Object as the put method argument.



V get(Object key)


Is there a way I can restrict the datatype which I pass as an argument in the get method?



The argument that I pass should have the same datatype as the datatype of the Key which I use while instantiating my hashmap.





This question already has an answer here:



  • What are the reasons why Map.get(Object key) is not (fully) generic

    11 answers







java hashmap






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 22 at 13:50









Peter Mortensen

14k1987114




14k1987114










asked Apr 22 at 7:04









RitoRito

1,117819




1,117819




marked as duplicate by Roddy of the Frozen Peas, KevinO, Community Apr 22 at 19:05


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.









marked as duplicate by Roddy of the Frozen Peas, KevinO, Community Apr 22 at 19:05


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.









  • 1





    No. But good IDEs will warn you when doing that. And you can encapsulate the map into your own class.

    – JB Nizet
    Apr 22 at 7:16











  • In other languages you could create extension method, like getTyped.... In Java you can do this with static method, so your call will be getTyped(map, key). Ugly, but works.

    – dyukha
    Apr 22 at 7:22












  • I have considered the option of creating a wrapper method over the get method, something like this: Integer getMapValue(Map map, String Key) return map.get(key) And call this method instead of the get method, but I wanted to know if Java provides any such restricting feature of not?

    – Rito
    Apr 22 at 7:30











  • You can add an implementation of a get(K key) method, but It seems like an unnecessary effort. The return value for a mismatching key (type-wise) will be null, as expected. So the Map will conform to its API.

    – Rann Lifshitz
    Apr 22 at 7:37












  • 1





    No. But good IDEs will warn you when doing that. And you can encapsulate the map into your own class.

    – JB Nizet
    Apr 22 at 7:16











  • In other languages you could create extension method, like getTyped.... In Java you can do this with static method, so your call will be getTyped(map, key). Ugly, but works.

    – dyukha
    Apr 22 at 7:22












  • I have considered the option of creating a wrapper method over the get method, something like this: Integer getMapValue(Map map, String Key) return map.get(key) And call this method instead of the get method, but I wanted to know if Java provides any such restricting feature of not?

    – Rito
    Apr 22 at 7:30











  • You can add an implementation of a get(K key) method, but It seems like an unnecessary effort. The return value for a mismatching key (type-wise) will be null, as expected. So the Map will conform to its API.

    – Rann Lifshitz
    Apr 22 at 7:37







1




1





No. But good IDEs will warn you when doing that. And you can encapsulate the map into your own class.

– JB Nizet
Apr 22 at 7:16





No. But good IDEs will warn you when doing that. And you can encapsulate the map into your own class.

– JB Nizet
Apr 22 at 7:16













In other languages you could create extension method, like getTyped.... In Java you can do this with static method, so your call will be getTyped(map, key). Ugly, but works.

– dyukha
Apr 22 at 7:22






In other languages you could create extension method, like getTyped.... In Java you can do this with static method, so your call will be getTyped(map, key). Ugly, but works.

– dyukha
Apr 22 at 7:22














I have considered the option of creating a wrapper method over the get method, something like this: Integer getMapValue(Map map, String Key) return map.get(key) And call this method instead of the get method, but I wanted to know if Java provides any such restricting feature of not?

– Rito
Apr 22 at 7:30





I have considered the option of creating a wrapper method over the get method, something like this: Integer getMapValue(Map map, String Key) return map.get(key) And call this method instead of the get method, but I wanted to know if Java provides any such restricting feature of not?

– Rito
Apr 22 at 7:30













You can add an implementation of a get(K key) method, but It seems like an unnecessary effort. The return value for a mismatching key (type-wise) will be null, as expected. So the Map will conform to its API.

– Rann Lifshitz
Apr 22 at 7:37





You can add an implementation of a get(K key) method, but It seems like an unnecessary effort. The return value for a mismatching key (type-wise) will be null, as expected. So the Map will conform to its API.

– Rann Lifshitz
Apr 22 at 7:37












2 Answers
2






active

oldest

votes


















17














It is designed that way, since during the get operation only the equals and hashCode is used to determine the object to be returned. The implementation of the get method does not check for the type of the Object used as the key.



In your example you are trying to get the value by passing a long like myHashMap.get(1L);, firstly the hash code of the object Long having the value 1L will be used to determine the bucket from which to look for. Next the equals method of the key is used to find out the exact entry of the map from which to return the value. And in a well-defined equals method there is always a check for the type:



public boolean equals(Object obj) 
if (obj instanceof Long) //here type is checked
return value == ((Long)obj).longValue();

return false;



So if the types are not equal, the equals method returns false and hence get also will return null.



In some cases such as when using List as a key, it may happen that you put an item in the map using an instance of say an ArrayList but you can successfully retrieve the same value with an instance of an LinkedList. As both implement the List interface.



Map<List<String>, String> myHashMap = new HashMap<>();
List<String> arrayList = new ArrayList<>();
List<String> linkedList = new LinkedList<>();
myHashMap.put(arrayList, "foo");
System.out.println(myHashMap.get(linkedList));


The above code will output in the console foo.



Here although the implementations are different but if you examine the equals method of ArrayList, it is only checking if the type is a List:



public boolean equals(Object o) 
if (o == this)
return true;


if (!(o instanceof List)) //checking type of super interface
return false;

...



The same is true for LinkedList.






share|improve this answer




















  • 2





    This is a good example of how an answer should be written in StackOverflow - well formulated, informative, with to-the-point code examples. Well done!

    – Rann Lifshitz
    Apr 22 at 8:04






  • 1





    This answer is failing to address the "compilation error" aspect of the question and missing the implicit question of why Map.get is declared to accept Object instead of the K parameterized type.

    – Miles
    Apr 22 at 9:53






  • 1





    @Miles that question has already been answered here and here.

    – Moira
    Apr 22 at 14:11












  • As per the first link @Moira posted the List example should have the map type be something like Map<ArrayList<String>, String> instead. If the key type is List<String> then V get(K key) will still work and compile fine with both ArrayList and LinkedList. Also this answer does not attempt to answer OP's actual question "Is there a way I can restrict the datatype which I pass as an argument in the get method?"

    – SamYonnou
    Apr 22 at 15:03







  • 1





    @SamYonnou with a map defined like this Map<ArrayList<String>, String>, get with a LinkedList<String> instance would still work and retrieve the correct value as in the equals method the instanceof is done w.r.t to List and both ArrayList and LinkedList instances would satisfy that as I mentioned in my answer. And for the actual question many people have already pointed out that it is unnecessary and provided sample code to do it either way. I also explained that with a well defined equals method why it won't be necessary. :)

    – Amardeep Bhowmick
    Apr 22 at 15:32


















4














I think if it is very important in a project that we control type in HashMap, we could extend HashMap and force using this class instead of HashMap like the below code.



We have all HashMap capabilities, and we should just use the getValue method instead of the get method.



import java.util.HashMap;

public class MyHashMap<K,V> extends HashMap<K,V>

public V getValue(K key)
return super.get(key);




Test class:



 public class Test 
public static void main(String[] args)
MyHashMap<String,Integer> map = new MyHashMap();







share|improve this answer




















  • 2





    A similar answer was posted maybe an hour ago and was then deleted by its poster...........

    – Rann Lifshitz
    Apr 22 at 8:02

















2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









17














It is designed that way, since during the get operation only the equals and hashCode is used to determine the object to be returned. The implementation of the get method does not check for the type of the Object used as the key.



In your example you are trying to get the value by passing a long like myHashMap.get(1L);, firstly the hash code of the object Long having the value 1L will be used to determine the bucket from which to look for. Next the equals method of the key is used to find out the exact entry of the map from which to return the value. And in a well-defined equals method there is always a check for the type:



public boolean equals(Object obj) 
if (obj instanceof Long) //here type is checked
return value == ((Long)obj).longValue();

return false;



So if the types are not equal, the equals method returns false and hence get also will return null.



In some cases such as when using List as a key, it may happen that you put an item in the map using an instance of say an ArrayList but you can successfully retrieve the same value with an instance of an LinkedList. As both implement the List interface.



Map<List<String>, String> myHashMap = new HashMap<>();
List<String> arrayList = new ArrayList<>();
List<String> linkedList = new LinkedList<>();
myHashMap.put(arrayList, "foo");
System.out.println(myHashMap.get(linkedList));


The above code will output in the console foo.



Here although the implementations are different but if you examine the equals method of ArrayList, it is only checking if the type is a List:



public boolean equals(Object o) 
if (o == this)
return true;


if (!(o instanceof List)) //checking type of super interface
return false;

...



The same is true for LinkedList.






share|improve this answer




















  • 2





    This is a good example of how an answer should be written in StackOverflow - well formulated, informative, with to-the-point code examples. Well done!

    – Rann Lifshitz
    Apr 22 at 8:04






  • 1





    This answer is failing to address the "compilation error" aspect of the question and missing the implicit question of why Map.get is declared to accept Object instead of the K parameterized type.

    – Miles
    Apr 22 at 9:53






  • 1





    @Miles that question has already been answered here and here.

    – Moira
    Apr 22 at 14:11












  • As per the first link @Moira posted the List example should have the map type be something like Map<ArrayList<String>, String> instead. If the key type is List<String> then V get(K key) will still work and compile fine with both ArrayList and LinkedList. Also this answer does not attempt to answer OP's actual question "Is there a way I can restrict the datatype which I pass as an argument in the get method?"

    – SamYonnou
    Apr 22 at 15:03







  • 1





    @SamYonnou with a map defined like this Map<ArrayList<String>, String>, get with a LinkedList<String> instance would still work and retrieve the correct value as in the equals method the instanceof is done w.r.t to List and both ArrayList and LinkedList instances would satisfy that as I mentioned in my answer. And for the actual question many people have already pointed out that it is unnecessary and provided sample code to do it either way. I also explained that with a well defined equals method why it won't be necessary. :)

    – Amardeep Bhowmick
    Apr 22 at 15:32















17














It is designed that way, since during the get operation only the equals and hashCode is used to determine the object to be returned. The implementation of the get method does not check for the type of the Object used as the key.



In your example you are trying to get the value by passing a long like myHashMap.get(1L);, firstly the hash code of the object Long having the value 1L will be used to determine the bucket from which to look for. Next the equals method of the key is used to find out the exact entry of the map from which to return the value. And in a well-defined equals method there is always a check for the type:



public boolean equals(Object obj) 
if (obj instanceof Long) //here type is checked
return value == ((Long)obj).longValue();

return false;



So if the types are not equal, the equals method returns false and hence get also will return null.



In some cases such as when using List as a key, it may happen that you put an item in the map using an instance of say an ArrayList but you can successfully retrieve the same value with an instance of an LinkedList. As both implement the List interface.



Map<List<String>, String> myHashMap = new HashMap<>();
List<String> arrayList = new ArrayList<>();
List<String> linkedList = new LinkedList<>();
myHashMap.put(arrayList, "foo");
System.out.println(myHashMap.get(linkedList));


The above code will output in the console foo.



Here although the implementations are different but if you examine the equals method of ArrayList, it is only checking if the type is a List:



public boolean equals(Object o) 
if (o == this)
return true;


if (!(o instanceof List)) //checking type of super interface
return false;

...



The same is true for LinkedList.






share|improve this answer




















  • 2





    This is a good example of how an answer should be written in StackOverflow - well formulated, informative, with to-the-point code examples. Well done!

    – Rann Lifshitz
    Apr 22 at 8:04






  • 1





    This answer is failing to address the "compilation error" aspect of the question and missing the implicit question of why Map.get is declared to accept Object instead of the K parameterized type.

    – Miles
    Apr 22 at 9:53






  • 1





    @Miles that question has already been answered here and here.

    – Moira
    Apr 22 at 14:11












  • As per the first link @Moira posted the List example should have the map type be something like Map<ArrayList<String>, String> instead. If the key type is List<String> then V get(K key) will still work and compile fine with both ArrayList and LinkedList. Also this answer does not attempt to answer OP's actual question "Is there a way I can restrict the datatype which I pass as an argument in the get method?"

    – SamYonnou
    Apr 22 at 15:03







  • 1





    @SamYonnou with a map defined like this Map<ArrayList<String>, String>, get with a LinkedList<String> instance would still work and retrieve the correct value as in the equals method the instanceof is done w.r.t to List and both ArrayList and LinkedList instances would satisfy that as I mentioned in my answer. And for the actual question many people have already pointed out that it is unnecessary and provided sample code to do it either way. I also explained that with a well defined equals method why it won't be necessary. :)

    – Amardeep Bhowmick
    Apr 22 at 15:32













17












17








17







It is designed that way, since during the get operation only the equals and hashCode is used to determine the object to be returned. The implementation of the get method does not check for the type of the Object used as the key.



In your example you are trying to get the value by passing a long like myHashMap.get(1L);, firstly the hash code of the object Long having the value 1L will be used to determine the bucket from which to look for. Next the equals method of the key is used to find out the exact entry of the map from which to return the value. And in a well-defined equals method there is always a check for the type:



public boolean equals(Object obj) 
if (obj instanceof Long) //here type is checked
return value == ((Long)obj).longValue();

return false;



So if the types are not equal, the equals method returns false and hence get also will return null.



In some cases such as when using List as a key, it may happen that you put an item in the map using an instance of say an ArrayList but you can successfully retrieve the same value with an instance of an LinkedList. As both implement the List interface.



Map<List<String>, String> myHashMap = new HashMap<>();
List<String> arrayList = new ArrayList<>();
List<String> linkedList = new LinkedList<>();
myHashMap.put(arrayList, "foo");
System.out.println(myHashMap.get(linkedList));


The above code will output in the console foo.



Here although the implementations are different but if you examine the equals method of ArrayList, it is only checking if the type is a List:



public boolean equals(Object o) 
if (o == this)
return true;


if (!(o instanceof List)) //checking type of super interface
return false;

...



The same is true for LinkedList.






share|improve this answer















It is designed that way, since during the get operation only the equals and hashCode is used to determine the object to be returned. The implementation of the get method does not check for the type of the Object used as the key.



In your example you are trying to get the value by passing a long like myHashMap.get(1L);, firstly the hash code of the object Long having the value 1L will be used to determine the bucket from which to look for. Next the equals method of the key is used to find out the exact entry of the map from which to return the value. And in a well-defined equals method there is always a check for the type:



public boolean equals(Object obj) 
if (obj instanceof Long) //here type is checked
return value == ((Long)obj).longValue();

return false;



So if the types are not equal, the equals method returns false and hence get also will return null.



In some cases such as when using List as a key, it may happen that you put an item in the map using an instance of say an ArrayList but you can successfully retrieve the same value with an instance of an LinkedList. As both implement the List interface.



Map<List<String>, String> myHashMap = new HashMap<>();
List<String> arrayList = new ArrayList<>();
List<String> linkedList = new LinkedList<>();
myHashMap.put(arrayList, "foo");
System.out.println(myHashMap.get(linkedList));


The above code will output in the console foo.



Here although the implementations are different but if you examine the equals method of ArrayList, it is only checking if the type is a List:



public boolean equals(Object o) 
if (o == this)
return true;


if (!(o instanceof List)) //checking type of super interface
return false;

...



The same is true for LinkedList.







share|improve this answer














share|improve this answer



share|improve this answer








edited Apr 22 at 8:00

























answered Apr 22 at 7:38









Amardeep BhowmickAmardeep Bhowmick

6,45121231




6,45121231







  • 2





    This is a good example of how an answer should be written in StackOverflow - well formulated, informative, with to-the-point code examples. Well done!

    – Rann Lifshitz
    Apr 22 at 8:04






  • 1





    This answer is failing to address the "compilation error" aspect of the question and missing the implicit question of why Map.get is declared to accept Object instead of the K parameterized type.

    – Miles
    Apr 22 at 9:53






  • 1





    @Miles that question has already been answered here and here.

    – Moira
    Apr 22 at 14:11












  • As per the first link @Moira posted the List example should have the map type be something like Map<ArrayList<String>, String> instead. If the key type is List<String> then V get(K key) will still work and compile fine with both ArrayList and LinkedList. Also this answer does not attempt to answer OP's actual question "Is there a way I can restrict the datatype which I pass as an argument in the get method?"

    – SamYonnou
    Apr 22 at 15:03







  • 1





    @SamYonnou with a map defined like this Map<ArrayList<String>, String>, get with a LinkedList<String> instance would still work and retrieve the correct value as in the equals method the instanceof is done w.r.t to List and both ArrayList and LinkedList instances would satisfy that as I mentioned in my answer. And for the actual question many people have already pointed out that it is unnecessary and provided sample code to do it either way. I also explained that with a well defined equals method why it won't be necessary. :)

    – Amardeep Bhowmick
    Apr 22 at 15:32












  • 2





    This is a good example of how an answer should be written in StackOverflow - well formulated, informative, with to-the-point code examples. Well done!

    – Rann Lifshitz
    Apr 22 at 8:04






  • 1





    This answer is failing to address the "compilation error" aspect of the question and missing the implicit question of why Map.get is declared to accept Object instead of the K parameterized type.

    – Miles
    Apr 22 at 9:53






  • 1





    @Miles that question has already been answered here and here.

    – Moira
    Apr 22 at 14:11












  • As per the first link @Moira posted the List example should have the map type be something like Map<ArrayList<String>, String> instead. If the key type is List<String> then V get(K key) will still work and compile fine with both ArrayList and LinkedList. Also this answer does not attempt to answer OP's actual question "Is there a way I can restrict the datatype which I pass as an argument in the get method?"

    – SamYonnou
    Apr 22 at 15:03







  • 1





    @SamYonnou with a map defined like this Map<ArrayList<String>, String>, get with a LinkedList<String> instance would still work and retrieve the correct value as in the equals method the instanceof is done w.r.t to List and both ArrayList and LinkedList instances would satisfy that as I mentioned in my answer. And for the actual question many people have already pointed out that it is unnecessary and provided sample code to do it either way. I also explained that with a well defined equals method why it won't be necessary. :)

    – Amardeep Bhowmick
    Apr 22 at 15:32







2




2





This is a good example of how an answer should be written in StackOverflow - well formulated, informative, with to-the-point code examples. Well done!

– Rann Lifshitz
Apr 22 at 8:04





This is a good example of how an answer should be written in StackOverflow - well formulated, informative, with to-the-point code examples. Well done!

– Rann Lifshitz
Apr 22 at 8:04




1




1





This answer is failing to address the "compilation error" aspect of the question and missing the implicit question of why Map.get is declared to accept Object instead of the K parameterized type.

– Miles
Apr 22 at 9:53





This answer is failing to address the "compilation error" aspect of the question and missing the implicit question of why Map.get is declared to accept Object instead of the K parameterized type.

– Miles
Apr 22 at 9:53




1




1





@Miles that question has already been answered here and here.

– Moira
Apr 22 at 14:11






@Miles that question has already been answered here and here.

– Moira
Apr 22 at 14:11














As per the first link @Moira posted the List example should have the map type be something like Map<ArrayList<String>, String> instead. If the key type is List<String> then V get(K key) will still work and compile fine with both ArrayList and LinkedList. Also this answer does not attempt to answer OP's actual question "Is there a way I can restrict the datatype which I pass as an argument in the get method?"

– SamYonnou
Apr 22 at 15:03






As per the first link @Moira posted the List example should have the map type be something like Map<ArrayList<String>, String> instead. If the key type is List<String> then V get(K key) will still work and compile fine with both ArrayList and LinkedList. Also this answer does not attempt to answer OP's actual question "Is there a way I can restrict the datatype which I pass as an argument in the get method?"

– SamYonnou
Apr 22 at 15:03





1




1





@SamYonnou with a map defined like this Map<ArrayList<String>, String>, get with a LinkedList<String> instance would still work and retrieve the correct value as in the equals method the instanceof is done w.r.t to List and both ArrayList and LinkedList instances would satisfy that as I mentioned in my answer. And for the actual question many people have already pointed out that it is unnecessary and provided sample code to do it either way. I also explained that with a well defined equals method why it won't be necessary. :)

– Amardeep Bhowmick
Apr 22 at 15:32





@SamYonnou with a map defined like this Map<ArrayList<String>, String>, get with a LinkedList<String> instance would still work and retrieve the correct value as in the equals method the instanceof is done w.r.t to List and both ArrayList and LinkedList instances would satisfy that as I mentioned in my answer. And for the actual question many people have already pointed out that it is unnecessary and provided sample code to do it either way. I also explained that with a well defined equals method why it won't be necessary. :)

– Amardeep Bhowmick
Apr 22 at 15:32













4














I think if it is very important in a project that we control type in HashMap, we could extend HashMap and force using this class instead of HashMap like the below code.



We have all HashMap capabilities, and we should just use the getValue method instead of the get method.



import java.util.HashMap;

public class MyHashMap<K,V> extends HashMap<K,V>

public V getValue(K key)
return super.get(key);




Test class:



 public class Test 
public static void main(String[] args)
MyHashMap<String,Integer> map = new MyHashMap();







share|improve this answer




















  • 2





    A similar answer was posted maybe an hour ago and was then deleted by its poster...........

    – Rann Lifshitz
    Apr 22 at 8:02















4














I think if it is very important in a project that we control type in HashMap, we could extend HashMap and force using this class instead of HashMap like the below code.



We have all HashMap capabilities, and we should just use the getValue method instead of the get method.



import java.util.HashMap;

public class MyHashMap<K,V> extends HashMap<K,V>

public V getValue(K key)
return super.get(key);




Test class:



 public class Test 
public static void main(String[] args)
MyHashMap<String,Integer> map = new MyHashMap();







share|improve this answer




















  • 2





    A similar answer was posted maybe an hour ago and was then deleted by its poster...........

    – Rann Lifshitz
    Apr 22 at 8:02













4












4








4







I think if it is very important in a project that we control type in HashMap, we could extend HashMap and force using this class instead of HashMap like the below code.



We have all HashMap capabilities, and we should just use the getValue method instead of the get method.



import java.util.HashMap;

public class MyHashMap<K,V> extends HashMap<K,V>

public V getValue(K key)
return super.get(key);




Test class:



 public class Test 
public static void main(String[] args)
MyHashMap<String,Integer> map = new MyHashMap();







share|improve this answer















I think if it is very important in a project that we control type in HashMap, we could extend HashMap and force using this class instead of HashMap like the below code.



We have all HashMap capabilities, and we should just use the getValue method instead of the get method.



import java.util.HashMap;

public class MyHashMap<K,V> extends HashMap<K,V>

public V getValue(K key)
return super.get(key);




Test class:



 public class Test 
public static void main(String[] args)
MyHashMap<String,Integer> map = new MyHashMap();








share|improve this answer














share|improve this answer



share|improve this answer








edited Apr 22 at 13:52









Peter Mortensen

14k1987114




14k1987114










answered Apr 22 at 8:01









hamid rostamihamid rostami

1117




1117







  • 2





    A similar answer was posted maybe an hour ago and was then deleted by its poster...........

    – Rann Lifshitz
    Apr 22 at 8:02












  • 2





    A similar answer was posted maybe an hour ago and was then deleted by its poster...........

    – Rann Lifshitz
    Apr 22 at 8:02







2




2





A similar answer was posted maybe an hour ago and was then deleted by its poster...........

– Rann Lifshitz
Apr 22 at 8:02





A similar answer was posted maybe an hour ago and was then deleted by its poster...........

– Rann Lifshitz
Apr 22 at 8:02



Popular posts from this blog

Bulk add to cart function issuecart vs. mini cart issue … rwd themeRedirect Add to cart button to cart pageAdd to cart issue - Magento 2.1The requested Payment Method is not available When creating an orderM2: reason add-to-cart might not function in production modeAdd to cart issue in some android devicesMagento 2 - custom price can not add to subtotal and grand total after add to cartAdd to cart codeIssue with my cart module on pdp and cart pages, just keeps spinningBulk price and quantity update using rest api

БиармияSxpst500bh2ntaf! 3h2r