vagd.gdb.xmethod
================

.. py:module:: vagd.gdb.xmethod


Classes
-------

.. autoapisummary::

   vagd.gdb.xmethod._XMethod
   vagd.gdb.xmethod.XMethod
   vagd.gdb.xmethod._XMethodWorker
   vagd.gdb.xmethod.XMethodWorker
   vagd.gdb.xmethod._XMethodMatcher
   vagd.gdb.xmethod.XMethodMatcher


Functions
---------

.. autoapisummary::

   vagd.gdb.xmethod.register_xmethod_matcher


Module Contents
---------------

.. py:function:: register_xmethod_matcher(locus: gdb.Objfile | gdb.Progspace | None, matcher: _XMethodMatcher, replace: bool = ...) -> None

.. py:class:: _XMethod

   Bases: :py:obj:`Protocol`


   Base class for protocol classes.

   Protocol classes are defined as::

       class Proto(Protocol):
           def meth(self) -> int:
               ...

   Such classes are primarily used with static type checkers that recognize
   structural subtyping (static duck-typing).

   For example::

       class C:
           def meth(self) -> int:
               return 0

       def func(x: Proto) -> int:
           return x.meth()

       func(C())  # Passes static type check

   See PEP 544 for details. Protocol classes decorated with
   @typing.runtime_checkable act as simple-minded runtime protocols that check
   only the presence of given attributes, ignoring their type signatures.
   Protocol classes can be generic, they are defined as::

       class GenProto[T](Protocol):
           def meth(self) -> T:
               ...


   .. py:attribute:: name
      :type:  str


   .. py:attribute:: enabled
      :type:  bool


.. py:class:: XMethod(name: str)

   .. py:attribute:: name
      :type:  str


   .. py:attribute:: enabled
      :type:  bool


.. py:class:: _XMethodWorker

   Bases: :py:obj:`Protocol`


   Base class for protocol classes.

   Protocol classes are defined as::

       class Proto(Protocol):
           def meth(self) -> int:
               ...

   Such classes are primarily used with static type checkers that recognize
   structural subtyping (static duck-typing).

   For example::

       class C:
           def meth(self) -> int:
               return 0

       def func(x: Proto) -> int:
           return x.meth()

       func(C())  # Passes static type check

   See PEP 544 for details. Protocol classes decorated with
   @typing.runtime_checkable act as simple-minded runtime protocols that check
   only the presence of given attributes, ignoring their type signatures.
   Protocol classes can be generic, they are defined as::

       class GenProto[T](Protocol):
           def meth(self) -> T:
               ...


   .. py:method:: get_arg_types() -> collections.abc.Sequence[gdb.Type]


   .. py:method:: get_result_type(*args: gdb.Value) -> gdb.Type


   .. py:method:: __call__(*args: gdb.Value) -> object


.. py:class:: XMethodWorker

.. py:class:: _XMethodMatcher(name: str)

   Bases: :py:obj:`Protocol`


   Base class for protocol classes.

   Protocol classes are defined as::

       class Proto(Protocol):
           def meth(self) -> int:
               ...

   Such classes are primarily used with static type checkers that recognize
   structural subtyping (static duck-typing).

   For example::

       class C:
           def meth(self) -> int:
               return 0

       def func(x: Proto) -> int:
           return x.meth()

       func(C())  # Passes static type check

   See PEP 544 for details. Protocol classes decorated with
   @typing.runtime_checkable act as simple-minded runtime protocols that check
   only the presence of given attributes, ignoring their type signatures.
   Protocol classes can be generic, they are defined as::

       class GenProto[T](Protocol):
           def meth(self) -> T:
               ...


   .. py:attribute:: enabled
      :type:  bool


   .. py:attribute:: methods
      :type:  list[_XMethod]


   .. py:method:: match(class_type: gdb.Type, method_name: str) -> _XMethodWorker


.. py:class:: XMethodMatcher