-
-
Notifications
You must be signed in to change notification settings - Fork 348
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
${parameter-default} vs ${parameter:-default} #871
Comments
Please note that we do not simplify Aside, the change that adds this simplification is not, as far as I can tell, in 3.5.0 nor 3.5.1 yet. It's not in the v3.5 branch from where I gather v3.5.1 was released, and it's in master only after v3.5.0 and v3.6.0-0.dev. |
@scop is right: the change is in master, but not in v3.5.1. It's not a bug fix, so it wasn't cherry-picked for a bugfix release. |
I see now. That all makes sense. I apparently was using the Anyway given the explanation you provided above, I don't feel like the syntax without |
In my view that flag is |
I think I'm happy to close this, unless anyone else feels the need to discuss the topic further. |
I'll leave this open for another week to see if anyone else has a new opinion or data to change our behavior. For now, I think we can keep the feature in master. |
Some people are confused by `latest` versus `v3`, so clarify that. Also document that we publish releases and Alpine variants. While here, remove the reference to the alternative Docker image, as these days it's somewhat redundant (we took ideas from it) and also currently out of date. See #740, #805, #871.
Some people are confused by `latest` versus `v3`, so clarify that. Also document that we publish releases and Alpine variants. While here, remove the reference to the alternative Docker image, as these days it's somewhat redundant (we took ideas from it) and also currently out of date. See #740, #805, #871.
Closing per the above. |
I noticed that shfmt 3.5.1 (maybe also 3.5.0, I haven't tested yet) wants
${parameter-default}
which has different behavior from${parameter:-default}
Ref: https://tldp.org/LDP/abs/html/parameter-substitution.html
I believe this change should be reverted. Both methods have different purposes and should be used accordingly.
The text was updated successfully, but these errors were encountered: