You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need special handling for protocols whose requirement
signature exists but is in a serialized state, as we
cannot run the StructuralRequirementsRequest on such
a protocol as there's no work to be done, effectively.
\item\texttt{getProtocolDependencies()} evaluates the \texttt{ProtocolDependenciesRequest}.
637
637
\end{itemize}
638
638
639
+
\IndexSource{protocol inverses request}
640
+
\apiref{ProtocolInversesRequest}{class}
641
+
A request evaluator request which enumerates the inverse requirements written on the given protocol and its associated types.
642
+
643
+
\apiref{ProtocolDecl}{class}
644
+
See also \SecRef{src:declarations}.
645
+
\begin{itemize}
646
+
\item\texttt{getInverseRequirements()} evaluates the \texttt{ProtocolInversesRequest}.
647
+
\end{itemize}
648
+
639
649
\IndexSource{requirement machine}
640
650
\apiref{rewriting::RequirementMachine}{class}
641
651
A list of rewrite rules and a property map. See also \SecRef{src:symbolstermsrules} and \SecRef{propertymapsourceref}. Entry points for initializing a requirement machine, called by the rewrite context and various requests:
0 commit comments