Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Binder limitations documentation added #229

Merged
merged 3 commits into from
Oct 11, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions documentation/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ Contents:
install
basics
config
limitations
examples
debugging
testing
Expand Down
87 changes: 87 additions & 0 deletions documentation/limitations.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,87 @@
Binder Limitations
##################

This section lists some of ``binder``'s more prominent limitations.

------------------
External Operators
------------------

Unlike C++, which allows operators to be defined outside of classes and redefined across different namespaces, python requires operators be member functions and thus lacks the ability to choose which overload to use based on context.
In line with this, ``binder`` will only bind (most) C++ operators if they are member functions (i.e. they cannot be defined externally).

These operators include, but are not necessarily limited to:

.. code-block:: console
operator~ (__invert__)

operator+ (__add__)
operator- (__sub__)
operator* (__mul__)
operator/ (__div__)
operator% (__mod__)

operator& (__and__)
operator| (__or__)
operator^ (__xor__)
operator<< (__lshift__)
operator>> (__rshift__)

operator+= (__iadd__)
operator-= (__isub__)
operator*= (__imul__)
operator/= (__idiv__)
operator%= (__imod__)

operator&= (__iand__)
operator|= (__ior__)
operator^= (__ixor__)
operator<<= (__ilshift__)
operator>>= (__irshift__)

operator() (__call__)
operator== (__eq__)
operator!= (__ne__)
operator[] (__getitem__)
operator= (assign)
operator++ (plus_plus)
operator-- (minus_minus)

-----------------
Ignored Operators
-----------------

The following operators will be ignored by binder:

.. code-block:: console

// Logical
&&
||

// Cast to T
explicit operator T()
operator T()

// Misc
,
new
new[]
delete
delete[]

-------------
Miscellaneous
-------------

1. The pre/post increment operators both map to ``plus_plus`, with the pre-increment operator being invoked via ``a.plus_plus()`` and post-increment via ``.plus_plus(0)``; just as the operators are technically defined in C++. The same is true for the pre/post decrement operators, both called ``minus_minus``.

2. User defined literals ``operator"" _foo`` end up being named as ``operator_foo``.

----------
Known Bugs
----------

1. The unary ``operator+`` and unary ``operator-`` currently map to ``__add__`` and ``__sub__`` rather than ``__pos__`` and ``__neg__``.

2. The unary ``operator*`` (dereference operator) will currently map to ``__mul__``.