You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Kevin Risden (Jira)" <ji...@apache.org> on 2023/03/22 13:44:00 UTC
[jira] [Created] (SOLR-16715) Replace new HashMap(int) and new HashSet(int) with CollectionUtil.newHashMap / CollectionUtil.newHashSet
Kevin Risden created SOLR-16715:
-----------------------------------
Summary: Replace new HashMap(int) and new HashSet(int) with CollectionUtil.newHashMap / CollectionUtil.newHashSet
Key: SOLR-16715
URL: https://issues.apache.org/jira/browse/SOLR-16715
Project: Solr
Issue Type: Task
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Kevin Risden
Assignee: Kevin Risden
While looking at replacing Guava, [~dsmiley] proposed converting existing new HashMap(int) and new HashSet(int) to avoid the trap of them not actually being that size.
https://github.com/apache/solr/pull/1466#discussion_r1144811614
We should be able to enforce this with ForbiddenAPIs and https://github.com/apache/solr/pull/1466 adds CollectionUtil inspired by Lucene that we can use.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org