You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
execute, try and call are reserved words, tryWith1 is a name the user has to came with
If user is lazy and do not want to invent names (which are useful, as far as I know just for error.instance feature), he might want to write this instead
As discussed in PM, this would go against one of the drives of the refactor, which is having proper references, and which you suggested, by the way.
Making names optional would IMO encourage users to malpractice for the sake of lazyness. Malpractice not only because it will make references more technical (using indexes), but also because of maintenance.
Using maps like we are doing now was a brilliant idea of yours, in my opinion:
We dont have to enforce some kind of loose name uniqueness control
We dont have to enforce naming conventions. Authors write what they want, upper, lower, whichever case as long as its a valid property name
It makes references pretty and allows instant identification of a (possibly faulty) component, even for a non-technical person
Currently we write
execute, try and call are reserved words, tryWith1 is a name the user has to came with
If user is lazy and do not want to invent names (which are useful, as far as I know just for
error.instance
feature), he might want to write this insteadThe text was updated successfully, but these errors were encountered: