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
Currently robotpy-build (a) doesn't know its a function and (b) fn is present in Foo, but only the overloads that are in Foo, not the ones that are in Bar.
I could imagine that we could setup functions that the base class makes available (maybe in its trampoline?) where the original base class .def statements are called, but they get added to the child class instead.
This would probably be annoying to set up, I'm not sure it's worth it.
The text was updated successfully, but these errors were encountered:
So if you have:
Currently robotpy-build (a) doesn't know its a function and (b)
fn
is present inFoo
, but only the overloads that are inFoo
, not the ones that are inBar
.I could imagine that we could setup functions that the base class makes available (maybe in its trampoline?) where the original base class
.def
statements are called, but they get added to the child class instead.This would probably be annoying to set up, I'm not sure it's worth it.
The text was updated successfully, but these errors were encountered: