Signature for MemoryView

Hello,

When a method accepts arguments that expose MemoryView, we cannot represent that in current RBS (v3.8.1) and type check by Steep fails. We need a way to represent an object which exposes MemoryView.

As just an idea, a special phantom module RBS::Marker::MemoryView might play a role in this case:

class AMemoryViewProducer
  include RBS::Marker::MemoryView
end

class AMemoryViewConsumer
  def consume_memory_view: (RBS::Marker::MemoryView) -> void
end

I think we need more discussion. How do you think?

Thanks.

Start by reviewing how RBS v3.8.1 represents objects that expose MemoryView and how Steep consumes those signatures. The issue proposes RBS::Marker::MemoryView but leaves the design open; done requires an agreed representation, documented behavior, and corresponding validation before implementation.