-
Notifications
You must be signed in to change notification settings - Fork 51
Use symbols instead of strings for option names #604
Copy link
Copy link
Open
Labels
breakingIntroduces changes that could break existing codeIntroduces changes that could break existing coderefactorDoes not change functionality, but makes the code better organized or more readableDoes not change functionality, but makes the code better organized or more readablewolfram languageRequires Wolfram Language implementationRequires Wolfram Language implementation
Description
Metadata
Metadata
Assignees
Labels
breakingIntroduces changes that could break existing codeIntroduces changes that could break existing coderefactorDoes not change functionality, but makes the code better organized or more readableDoes not change functionality, but makes the code better organized or more readablewolfram languageRequires Wolfram Language implementationRequires Wolfram Language implementation
The problem
We currently prefer using strings over symbols for options. This, however, is not consistent with conventions even for new
System`*symbols in Wolfram Language. As a result, some of our options (ones identical to existingSystem`ones) use symbols and some use strings. Users are then required to remember which one is which.Possible solution
I suggest to switch to using symbols for option names. This will require writing usage message for each of them and making sure they don't conflict with system symbols and other packages.