Replies: 3 comments
-
That actually makes it much likely to be chosen over introducing a new one. Besides that, I would find |
Beta Was this translation helpful? Give feedback.
-
@miloush I mean we might have each of those word being used as variable name in the past var delete = Http.Request("DELETE",url).Response();
if(delete.HttpStatuscode == 200)
//dosomething; But |
Beta Was this translation helpful? Give feedback.
-
I understand your concern, but that is usually not a problem, since there is no situation in which you could use the variable the way you propose the keyword to be used. This has been done many times in the past, for example with the On the other side, I do see the value in matching the name of the method. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
For manipulating dynamic object for interop with dynamic language or other service by json or any other dynamic data format. Ability to delete member is necessary to completely satisfied contract, making data that exclude the member instead of null
And it already supported by
TryDeleteMember
API ofDynamicObject
. Only need keyword to expose that functionalitySo I would suggest reusing
remove
keyword in contextually in front of dynamic objectdynamic object cannot be assumed that it could use function member. So we can't use
dynamicObj.Remove
or anything like that. Because it will be ambiguous if that object also have member in that name. So keyword to operate on it is necessaryAlternative
We could introduce new keyword. Normally it would be
delete
. I just think we already haveremove
being keyword so it would be less likely to be used thandelete
Beta Was this translation helpful? Give feedback.
All reactions