Is it possible to use an object of the User class with mutable attributes as a key in a HashMap, and what are the consequences of doing so?

Using an object of the User class with mutable attributes as a key in a HashMap is possible, but it is very dangerous and generally not recommended.

HashMap in Java uses the hashCode() and equals() methods of the key to determine the position and search for the element. If the attributes of the object involved in the calculation of hashCode() or equals() are changed after placing the object in the HashMap, then:

• The hash code will change, and the object will end up in the "wrong" bucket.
• Searching by key may not find the object because it has "lost" its place in the structure.
• This will lead to errors when retrieving, deleting, or updating elements.

Therefore, keys in HashMap should be immutable or at least not change the fields involved in hashCode() and equals().

If you need to use a mutable object as a key, it is better to:

• Make the key immutable (for example, use only the ID).
• Do not change the fields affecting hashCode() and equals() while the object is in the HashMap.

Example of the problem:

User user = new User("Alice", 25);
map.put(user, "data");
user.setName("Bob"); // Attribute affecting hashCode() has changed
map.get(user); // May return null because the key is "lost"