2016-04-07 08:31:01 +00:00
|
|
|
Limitations
|
|
|
|
|
###########
|
|
|
|
|
|
|
|
|
|
pybind11 strives to be a general solution to binding generation, but it also has
|
|
|
|
|
certain limitations:
|
|
|
|
|
|
|
|
|
|
- pybind11 casts away ``const``-ness in function arguments and return values.
|
|
|
|
|
This is in line with the Python language, which has no concept of ``const``
|
|
|
|
|
values. This means that some additional care is needed to avoid bugs that
|
|
|
|
|
would be caught by the type checker in a traditional C++ program.
|
|
|
|
|
|
2016-06-30 12:45:57 +00:00
|
|
|
- The NumPy interface ``pybind11::array`` greatly simplifies accessing
|
|
|
|
|
numerical data from C++ (and vice versa), but it's not a full-blown array
|
|
|
|
|
class like ``Eigen::Array`` or ``boost.multi_array``.
|
|
|
|
|
|
2016-09-11 11:00:40 +00:00
|
|
|
These features could be implemented but would lead to a significant increase in
|
|
|
|
|
complexity. I've decided to draw the line here to keep this project simple and
|
|
|
|
|
compact. Users who absolutely require these features are encouraged to fork
|
|
|
|
|
pybind11.
|
