Classes like cv::Algorithm can have a few subclasses, and in the Evision.Algorithm module, functions that accepts cv:: Algorithm parameters are expecting Evision.Algorithm.t() in their type specs.
Currently, although subclasses will have their own copies of these functions from the parent classes with correct type specs, we can find all derived classes of a class, and expand the type specs to accept them.
For example, say we have class Foo, and class Bar and Buzz are derived from Foo, then we're expecting the following changes:
Classes like
cv::Algorithmcan have a few subclasses, and in theEvision.Algorithmmodule, functions that acceptscv:: Algorithmparameters are expectingEvision.Algorithm.t()in their type specs.Currently, although subclasses will have their own copies of these functions from the parent classes with correct type specs, we can find all derived classes of a class, and expand the type specs to accept them.
For example, say we have class
Foo, and classBarandBuzzare derived fromFoo, then we're expecting the following changes:Before
After
This issue is not urgent but definitely can help users, the language server and tools like dialyzer.