Add caller func name into type_info.json to make it clear which function is doing wrong #116
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this pr does
Why I do this
I think this is really necessary in a kind of big project.
Let's think if you have a code like this.
This generates type_info like below.
Then, you would come up with the idea like "this gcd function must accept only int. Which function uses in wrong way...?".
However, you can't see any information about that. So you need to dig yourself which code was wrong. I spent the most of time on this while using pyannotate.
Now, this pr will show which code screwed up. This will generate type_info like below
As you see, you can understand
(str, str)
is called by"gcd.main : 4"
easily.remarks
I submitted Contributor License Agreement.