-
Notifications
You must be signed in to change notification settings - Fork 3
Description
Excerpt from #104:
We don't need to change the language semantics to implement the ask commands you're talking about; the things performing the action simply need to scan gidget before they act upon him. You just have to rewrite the code for their actions.
Are there cases where you want to explicitly send Gidget as an argument to an ask, where you don't want him to have to scan himself first?
Comment
We don't need to change the language semantics to implement the ask commands you're talking about; the things performing the action simply need to scan gidget before they act upon him. You just have to rewrite the code for their actions. Are there cases where you want to explicitly send Gidget as an argument to an ask, where you don't want him to have to scan himself first?
or cancel
mjslee 11 minutes ago | link | edit | delete
At the moment, there are no cases when you would have to explicitly state that you want gidget to be the recipient of the ask.
However, here is a future scenario that I could think of where we might want something like this (but not in our current scope of things for the pilot). "Oil can" can be used on Gidget or a button. In this case, you have to be specific about the entity you want the oil can to ask on. "ask oilcan to lube gidget" vs "ask oilcan to lube button".