Simer

Related task #319 requires `@specialized(Byte)` applied to `Slice` which in my IntelliJ setup does not register breakpoints. To make debugging/breakpoints work remove `@specialized(Byte)` from `Slice.scala`.

@hemantgs sorry I've had to attempt at this task because I'm running some benchmarks and `ByteOps` needs to be removed. This commit is preview only. ## Progress All Java APIs...

The prefixes for Java APIs is inconvenient. There is a better way of doing this so Java APIs are seamless. I'm going to remove "good first issue" label and work...

Ah! IntelliJ debugger is not happy with these annotations. Breakpoints do not get registered.

[Foreign-memory access API](https://openjdk.java.net/jeps/393) although in incubation is actually a well tested API since Java 14. Another option is to use `sun.misc.Unsafe` if Java 8 builds are important for us. After...

> Are you testing with J8 (which is EOL in 4 months) or J11? J8 up until now. I didn't know about the EOL. Thanks for letting me know. >...

You are right and this is a known problem. The need for boxing should be removed. Largest majority of heap allocated objects are of type `Byte`, removing these would get...

> I'd suggest make it generic via `InputStream` and `OutputStream`. By "it" do you mean the `Serializer` API or the data types (Map, Set etc) API? I'm guessing you mean...

Was your configured `mapSize` greater than `Int.MaxValue - 2` at any time? `Int.MaxValue` is too large. You will see the same error with `new Array[Byte](Int.MaxValue)`. #280 will resolve this but...

We have to limit file sizes for now. Caching and other processes make uses of byte arrays (`Array[Byte]`) which are limited to **2.14.GB** on the JVM so file size limits...