forked from stephenslab/dsc
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Handle parameter name conflict with Python keywords #7
Comments
@lmxy0212 here is one parser & syntax issue. I'll post more here. It would be helpful if you |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For example, a module parameter
lambda
is going to trigger an error message because it conflicts wiht Pythons
labmda
function.We can definitely ban people from using parameters that conflicts with Python. But for R users, the
lambda
keyword is very innocent so disallowing users to use parameters like this seems a bit limiting.We may do something on the parser's end to remove this restriction? For example instead of putting:
in DSC generated script, we always wrap it to a dictionary, eg
The text was updated successfully, but these errors were encountered: