-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
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
Confusion in inst2vec_preprocess.py when reading code #28
Comments
The assertion is correct. It checks for different regular expressions, and if there is no match continues to the next one. If the last check fails, then Why do you think it should be the opposite? |
I think that if it goes to the branch But in this case, assertion in this brach will always fail. Does it mean that this brach should just not be executed? |
Or it is the debug code left after testing the function find_outer_most_last_parenthesis. If it is that case, I understand it and the comments there. When I first see it, I just got confused and didn't realize the meaning of this code. |
Yes, the assertion and regexp in the branch is a sanity check meant to make sure that |
Thanks for your reply! Thanks for your outstanding work! I really learn a lot from it. |
Happy to help :) |
When I reading code in inst2vec_preprocess.py, I find in line 865 that
assert check is not None, "Could not match argument list in:\n" + line + "\nFunction:\n" + func_name
may have to change to
assert check is None.
But I'm confused and don't know whether I should change it.
The text was updated successfully, but these errors were encountered: