-
Notifications
You must be signed in to change notification settings - Fork 139
Bring back the previous behavior of call_guest_function_by_name
#761
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
base: main
Are you sure you want to change the base?
Conversation
ee49c52
to
d99d24b
Compare
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.
LGTM!
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.
Looks good to me
fc3eb8c
to
4026423
Compare
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.
LGTM. I guess we decided we don't care about the Callable trait?
It looks like we need to provide a way for this to choose the behavior, or we need to break it/keep current behavior |
Signed-off-by: Jorge Prendes <[email protected]>
Signed-off-by: Jorge Prendes <[email protected]>
Signed-off-by: Jorge Prendes <[email protected]>
Signed-off-by: Jorge Prendes <[email protected]>
Signed-off-by: Jorge Prendes <[email protected]>
This PR brings back the previous behaviour of
call_guest_function_by_name
, and exposes the new behavioud behind a different name:run
.Originally I wanted to call the new behaviour
call
, but that method exists as an alias tocall_guest_function_by_name
throughtCallable
trait.The risk of using the
call
name is that anyone using theCallable
trait would get an (almost) silent change in behaviour (almost because there would be a lint aboutCallable
being unused).Let me know if anyone prefers a different name.