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
The cpp-linter-rs API is finally lamenting into a stable v2 API.
I think it would be beneficial for the bindings to have some API that we can use for reproduction of incoming issues.
The v1 (pure-python) API was very handy at reproducing reported issues because I could track down which function was misbehaving.
While async support in the node.js binding (via napi-rs) should be adequate, the python binding (via pyo3) has very limited support for async API (via pyo3-async-runtimes).
Warning
The python API may or may not be backward compatible with cpp-linter v1 API.
It may be easier to write thin wrappers around the rust API, but this is kind of a pain because thin wrappers do not inherit docs from the rust API.
The cpp-linter-rs API is finally lamenting into a stable v2 API.
I think it would be beneficial for the bindings to have some API that we can use for reproduction of incoming issues.
The v1 (pure-python) API was very handy at reproducing reported issues because I could track down which function was misbehaving.
While async support in the node.js binding (via napi-rs) should be adequate, the python binding (via pyo3) has very limited support for async API (via pyo3-async-runtimes).
Warning
The python API may or may not be backward compatible with cpp-linter v1 API.
It may be easier to write thin wrappers around the rust API, but this is kind of a pain because thin wrappers do not inherit docs from the rust API.