Due to a performance profiling hotspot detailed here here, I implemented my own BitSet using Java's BitSet. This is intended to replace the Enumeration.ValueSet. However, it's a bit awkward to use, primarily due to my likely misunderstanding of the relationships between the Enumeration class, Enumeration type and concrete Enumeration object.
Due to a performance profiling hotspot detailed here, I implemented my own BitSet using Java's BitSet. This is intended to replace the Enumeration.ValueSet. However, it's a bit awkward to use, primarily due to my likely misunderstanding of the relationships between the Enumeration class, Enumeration type and concrete Enumeration object.
Due to a performance profiling hotspot detailed here, I implemented my own BitSet using Java's BitSet. This is intended to replace the Enumeration.ValueSet. However, it's a bit awkward to use, primarily due to my likely misunderstanding of the relationships between the Enumeration class, Enumeration type and concrete Enumeration object.
Due to a performance profiling hot spothotspot detailed in http://stackoverflow.com/questions/27632554/scala-enumeration-valueset-slow-replacement-based-on-java-bitsethere, I implemented my own BitSetBitSet using Java's BitSetBitSet. This is intended to replace the Enumeration.ValueSetEnumeration.ValueSet. However, it's a bit awkward to use, primarily due to my likely misunderstanding of the relationships between the EnumerationEnumeration class, EnumerationEnumeration type and concrete EnumerationEnumeration object.
For mkStringmkString I need to actually pass in the enumeration object itself. Is there any way to make this entire edifice a little more user-friendly?
Due to a performance profiling hot spot detailed in http://stackoverflow.com/questions/27632554/scala-enumeration-valueset-slow-replacement-based-on-java-bitset, I implemented my own BitSet using Java's BitSet. This is intended to replace the Enumeration.ValueSet. However, it's a bit awkward to use, primarily due to my likely misunderstanding of the relationships between the Enumeration class, Enumeration type and concrete Enumeration object.
For mkString I need to actually pass in the enumeration object itself. Is there any way to make this entire edifice a little more user-friendly?
Due to a performance profiling hotspot detailed here, I implemented my own BitSet using Java's BitSet. This is intended to replace the Enumeration.ValueSet. However, it's a bit awkward to use, primarily due to my likely misunderstanding of the relationships between the Enumeration class, Enumeration type and concrete Enumeration object.
For mkString I need to actually pass in the enumeration object itself. Is there any way to make this entire edifice a little more user-friendly?