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
I imagine some people will be confused when upgrading to the changed default if they have any scripts that contain Bash syntax but look like POSIX shell scripts. If the parser error message ends with something like (parsed as posix via -ln=auto), then hopefully that would be less confusing.
The text was updated successfully, but these errors were encountered:
explicitly state language dialect on `syntax.LangError`s when ln
is set to `auto`
for example, incompatible bash constructs will cause parse errors
due to the parser using posix as language dialect
fixesmvdan#803
explicitly state language dialect on `syntax.LangError`s when ln
is set to `auto`
for example, incompatible bash constructs will cause parse errors
due to the parser using posix as language dialect
fixes#803
I imagine some people will be confused when upgrading to the changed default if they have any scripts that contain Bash syntax but look like POSIX shell scripts. If the parser error message ends with something like
(parsed as posix via -ln=auto)
, then hopefully that would be less confusing.The text was updated successfully, but these errors were encountered: