Wenzel Jakob | 1e1f367 | 2016-04-07 10:31:01 +0200 | [diff] [blame^] | 1 | Limitations |
| 2 | ########### |
| 3 | |
| 4 | pybind11 strives to be a general solution to binding generation, but it also has |
| 5 | certain limitations: |
| 6 | |
| 7 | - pybind11 casts away ``const``-ness in function arguments and return values. |
| 8 | This is in line with the Python language, which has no concept of ``const`` |
| 9 | values. This means that some additional care is needed to avoid bugs that |
| 10 | would be caught by the type checker in a traditional C++ program. |
| 11 | |
| 12 | - Multiple inheritance relationships on the C++ side cannot be mapped to |
| 13 | Python. |
| 14 | |
| 15 | Both of these features could be implemented but would lead to a significant |
| 16 | increase in complexity. I've decided to draw the line here to keep this project |
| 17 | simple and compact. Users who absolutely require these features are encouraged |
| 18 | to fork pybind11. |
| 19 | |