Yes, in a strict code sense, it’s three declarations, but we’re talking about someone else reading the code. So the outer module is like a document body, and the inner module is like a paragraph.
This convention is targeted toward the reader of the code, so if they’re working in the module, they will already know to use %State{}. The idea is that the reader should be able to search for State in the code and have a single place to look to find out what it is.
This is only true for functions:
defmodule TestModule do
defstruct [:test]
@type x :: integer()
@type y :: integer()
@type z :: integer()
@type a :: integer()
@type n :: integer()
@type m :: integer()
@type o :: integer()
@spec hello_world :: :ok
def hello_world do
:ok
end
@type t :: %__MODULE__{test: nil | :test}
end
This will not raise any errors in v1.13.3
