<mime-type type="application/mbox">
    <!-- MBOX files start with "From [sender] [date]" -->
    <!-- To avoid false matches, check for other headers after that -->

    <magic priority="70">
      <match value="From " type="string" offset="0">
        <match value="\nFrom: " type="string" offset="32:256"/>
        <match value="\nDate: " type="string" offset="32:256"/>
        <match value="\nSubject: " type="string" offset="32:256"/>

and RHS match (become identical or assignment-compatible, depending on
context).
To that effect, type inference maintains a map of bound type parameters
to inferred type arguments; this map is consulted and updated during type unification.
Initially, the bound type parameters are known but the map is empty.
During type unification, if a new type argument <code>A</code> is inferred,

pkg syscall (netbsd-arm64-cgo), type Kevent_t struct, Ident uint64
pkg syscall (netbsd-arm64-cgo), type Kevent_t struct, Pad_cgo_0 [4]uint8
pkg syscall (netbsd-arm64-cgo), type Kevent_t struct, Udata int64
pkg syscall (netbsd-arm64-cgo), type Mclpool [0]uint8
pkg syscall (netbsd-arm64-cgo), type Msghdr struct
pkg syscall (netbsd-arm64-cgo), type Msghdr struct, Controllen uint32