[Bug] Rule Sheet Violation #8
Labels
No Label
Documentated
Implemented
Tested
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Speiger/Primitive-Collections#8
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The get & contains & remove method using Objects are right now converted to type-specific methods, now that is fine in most cases but there are cases where non-type-specific methods are really useful. Because Compare-Method is: Input.equals(collectionValue), that means the input decides if the key matches it should still work.
Adding an Object is a different story there the function should be converted to a type Specific method.
As an example: In a IntList a Integer should be able to remove an entry, but also a MutableInt from the Apache Library and a custom class that masks itself with a Integer. Since the Integer is final that is not possible with the type specific case.
I know of many cases where using that fact helped simplify a lot of code and it is intended by the Java Developers.