-
Notifications
You must be signed in to change notification settings - Fork 31
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
Record tag error message includes record name instead of only "userdata" #595
Merged
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
1784edb
record tag err msg includes record name
Vipul-Cariappa f06f29c
updated the failing test
Vipul-Cariappa e2ff586
implement code review suggestions
Vipul-Cariappa e23303f
removed `pallene_tag_name` and updated `pallene_type_tag` to work lik…
Vipul-Cariappa File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we still need
pallene_tag_name
, now that we havepallene_type_name
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We would require both
pallene_tag_name
andpallene_type_name
. They are different in two ways.const char *pallene_tag_name(int raw_tag)
andconst char *pallene_type_name(lua_State *L, const TValue *v)
expected_type
is known at the compile time (and usespallene_tag_name
) i.e. the argument's expected type. Whereas the argumentconst TValue *v
passed topallene_type_name
cannot be known at compile time.v
is the type of the actual argument passed at runtime.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIRC, there aren't any other places that call
pallene_tag_name
. The tag name function was there only for the error messages andpallene_type_name
now does that job. Notice how both functions are currently quite similar.If your goal was that the expected_type be known at compile time, then calling
pallene_tag_name
is not the way to do that. That C function call will only happen at run-time.One last thing: In the coder.lua, please use different variable names for the type tag returned by
pallene_type_tag
and for the type name that you compute inside the if statement.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please have a look at the recent changes. Hope the latest commit resolves the issues/suggestions you mentioned.