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
I'd expect a library as widely used as NCNN to have full documentation of its API. The documentation links I found are scattered over various websites and they all contain tips on how to use a subset of features. It's frustrating to have to guess the return types and arguments of functions, or indeed the function names, especially when using languages like Python where type hinting is optional.
Also, it's impossible to tell whether the API changed from release to release. Is there a reason why releases aren't semantically versioned?
Is there a plan to document the NCNN Python API? Or is it already documented and I'm missing a link?
The text was updated successfully, but these errors were encountered:
I'd expect a library as widely used as NCNN to have full documentation of its API. The documentation links I found are scattered over various websites and they all contain tips on how to use a subset of features. It's frustrating to have to guess the return types and arguments of functions, or indeed the function names, especially when using languages like Python where type hinting is optional.
Also, it's impossible to tell whether the API changed from release to release. Is there a reason why releases aren't semantically versioned?
Is there a plan to document the NCNN Python API? Or is it already documented and I'm missing a link?
The text was updated successfully, but these errors were encountered: