Calling MappedBytes.mappedBytes() with readOnly=true leaves realReadRemaining to 0 about chronicle-bytes

[JerryShea]

Assigning to you @peter-lawrey to decide what to do

[yevgenp]

Hi @vinjana.
Creating a read-only MappedBytes implies no write operation is allowed on the instance/file (regardless of the write position returned). Thus setting writePosition makes no sense.
readRemaining() works as specified in the JavaDoc and returns The number of bytes that can still be read.
Thus there is contradiction/counterintuitive behavior.