We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug Report
When C/C++ signatures are included in the C modules docstring. It is parsed as an overload.
To Reproduce
This script for examples outputs 2 signatures:
import mypy.stubdoc sigs = mypy.stubdoc.infer_sig_from_docstring( """ addLane(data: MyStruct) -> None C++: addLane(const MyStruct data) --> void """, "addLane", ) if sigs is not None: for sig in sigs: print(sig)
Expected Behavior
There should only be one signature in the resulting stub.
Actual Behavior
there are two signatures produced
FunctionSig(name='addLane', args=[ArgSig(name='data', type='MyStruct', default=False)], ret_type='None') FunctionSig(name='addLane', args=[ArgSig(name='constMyStructdata', type=None, default=False)], ret_type='void')
Your Environment
I have a pull request to solve this, #17658
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Bug Report
When C/C++ signatures are included in the C modules docstring. It is parsed as an overload.
To Reproduce
This script for examples outputs 2 signatures:
Expected Behavior
There should only be one signature in the resulting stub.
Actual Behavior
there are two signatures produced
Your Environment
I have a pull request to solve this, #17658
The text was updated successfully, but these errors were encountered: