-
-
Notifications
You must be signed in to change notification settings - Fork 163
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
Clean up oversights and leftovers for array refactoring #2223
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think changing the user-facing strings may not be worth it, because we have to change it back later
osh/sh_expr_eval.py
Outdated
raise error.TypeErr(val, 'Expected BashArray or BashAssoc', | ||
blame_loc) | ||
raise error.TypeErr( | ||
val, 'Expected BashArray, SparseArray, or BashAssoc', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are eventually going to remove change SparseArray -> BashArray, so this change will have to be undone
Since it is a user-facing string
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even if it would be finally switched, I wanted to carry out the switching in a single consistent commit.
I dropped commit 8e3f4b1. I've already modified the other error messages, but they are not reverted within this PR.
ed5b029
to
9137175
Compare
Great, thanks |
No description provided.