On Fri, Feb 16, 2024 at 11:32 AM Chet Ramey <chet.ra...@case.edu> wrote: > > On 2/13/24 12:41 PM, Grisha Levit wrote: > > On Wed, Jan 31, 2024, 14:10 Chet Ramey <chet.ra...@case.edu > > <mailto:chet.ra...@case.edu>> wrote: > > > > Well, is this a "my arm hurts when I do this" problem, or should bash > > restrict the types of attributes that can be set on readonly variables? > > > > For the attributes that only affect future assignments ([iluc]), I think > > think it makes sense to either (a) restrict the ability to change these > > attributes on readonly variables or (b) make internal assignments that > > force new values on readonly variables ignore such attributes. > > Let's say we take the approach of restricting attribute changes on readonly > variables to export/trace/local. > > Should it be an error to attempt to set other attributes (it already is > with nameref), or should declare silently ignore it?
I think an error (probably just the usual sh_readonly one) would be good.