[
https://issues.apache.org/jira/browse/CALCITE-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206950#comment-14206950
]
Julian Hyde commented on CALCITE-460:
-------------------------------------
Take a look at how ImmutableBitSet is used. There are 2 distinct modes of
operation: for one set operation, or a sequence of single-bit operations. I
figured that the check is worthwhile for the former but not the latter, so I
put the check into the ImmutableBitSet method (e.g. union) rather than the
Builder. But I don't feel strongly about it.
> Add ImmutableBitSet and replace uses of BitSet
> ----------------------------------------------
>
> Key: CALCITE-460
> URL: https://issues.apache.org/jira/browse/CALCITE-460
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
>
> Calcite makes heavy use of bit sets. java.util.BitSet has a convenient API
> but (a) is mutable, (b) uses quite a lot of memory, (c) is not iterable.
> Propose to implement ImmutableBitSet, which addresses those deficiencies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
