Does the SafeBuffer.Read method change the current position?

[udaken]

The Remarks section for the SafeBuffer.AcquirePointer method states the following:

AcquirePointer calls the SafeHandle.DangerousAddRef method and exposes the pointer. Unlike the Read method, it does not change the current position of the pointer.

However, SafeBuffer.Read does not have the similar remark.

When I prepared a test program to verify this, I did not observe any behavior that changes the current position.

Could this be a documentation bug?

using System.IO.MemoryMappedFiles;

File.WriteAllBytes("a.bin", new byte[]{0x1, 0x02, 0x03});
using(var mmf =  System.IO.MemoryMappedFiles.MemoryMappedFile.CreateFromFile("a.bin"))
{
  using (var accessor = mmf.CreateViewAccessor())
  {
     Console.WriteLine( $"{accessor.SafeMemoryMappedViewHandle.Read<byte>(0):X}"); // 1
     Console.WriteLine( $"{accessor.SafeMemoryMappedViewHandle.Read<byte>(0):X}"); // 1
     Console.WriteLine( $"{accessor.SafeMemoryMappedViewHandle.Read<byte>(0):X}"); // 1
  }
}

[teo-tsirpanis]

The documentation seems wrong. SafeBuffer does not have a notion of "current position"; all its read/write methods take the offset as a parameter.