On 12/8/18 8:30 PM, Grisha Levit wrote:
> There seems to be an issue with the following new bash-5.0 feature:
>
> A nameref name resolution loop in a function now resolves to a variable by
> that name in the global scope.
>
> [ Note: "warning: x: circular name reference" messages omitted belo
On 12/8/18 11:45 PM, Grisha Levit wrote:
> FWIW, namerefs in the temporary environment bypass the implemented checks:
>
> $ declare -n ref=var[0]
> $ ref=X printenv 'var[0]'
> X
Thanks for the report. We should follow namerefs, but in this case not
allow nameref values that aren't val
On 12/9/18 1:28 AM, Grisha Levit wrote:
> When a nameref local to a higher function scope points to a variable in the
> temporary environment, that nameref (correctly, it seems) expands to the
> value
> of the target variable from the temporary environment. However, assignment
> to
> the nameref mo
