[ruby-core:91609] [Ruby trunk Bug#15616] Chained destructive methods fail when using +@to unfreeze a frozen string

[ruby-core:91609] [Ruby trunk Bug#15616] Chained destructive methods fail when using +@to unfreeze a frozen string

[cianol]

Issue #15616 has been reported by cianooooo (Cian O).

----------------------------------------
Bug #15616: Chained destructive methods fail when using +@ to unfreeze a frozen string
https://bugs.ruby-lang.org/issues/15616

* Author: cianooooo (Cian O)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 2.6.1
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
Using the +@ syntax to unfreeze a string does not work when chaining destructive methods

Consider the following;
``` ruby
foo = "bar".freeze
+foo.gsub!("bar", "car")
```

This raises;
``` ruby
FrozenError: can't modify frozen String
```

However, I would have expected this to work since +@ should return a duplicated mutable string.



-- 
https://bugs.ruby-lang.org/

[ruby-core:91610] [Ruby trunk Bug#15616] Chained destructive methods fail when using +@to unfreeze a frozen string

[pdahorek]

Issue #15616 has been updated by ahorek (Pavel Rosický).


```
+foo.gsub!("bar", "car")
```
 stands for
```
+(foo.gsub!("bar", "car"))
```
and because foo is frozen, you'll get an error, see #15606


try this
```
foo = "bar".freeze
foo = (+foo).gsub!("bar", "car")
```
or
```
foo = "bar".freeze
foo = foo.gsub("bar", "car")
```


----------------------------------------
Bug #15616: Chained destructive methods fail when using +@ to unfreeze a frozen string
https://bugs.ruby-lang.org/issues/15616#change-76877

* Author: cianooooo (Cian O)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 2.6.1
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
Using the +@ syntax to unfreeze a string does not work when chaining destructive methods

Consider the following;
``` ruby
foo = "bar".freeze
+foo.gsub!("bar", "car")
```

This raises;
``` ruby
FrozenError: can't modify frozen String
```

However, I would have expected this to work since +@ should return a duplicated mutable string.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

[ruby-core:91619] [Ruby trunk Bug#15616] Chained destructive methods fail when using +@ to unfreeze a frozen string

[duerst]

Issue #15616 has been updated by duerst (Martin Dürst).

Status changed from Open to Rejected

Yes. It's a matter of precedence. The "Pickaxe" book describes it as

> Single terms in an expression may be any of the following:
> 
> [some cases omitted]
> 
> - Method invocation

That means that in ```+foo.gsub!("bar", "car")```, the `.` of method invocation has higher precedence than the `+`, and so you need to use parentheses if you want to change the order of evaluation.

----------------------------------------
Bug #15616: Chained destructive methods fail when using +@ to unfreeze a frozen string
https://bugs.ruby-lang.org/issues/15616#change-76883

* Author: cianooooo (Cian O)
* Status: Rejected
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 2.6.1
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
Using the +@ syntax to unfreeze a string does not work when chaining destructive methods

Consider the following;
``` ruby
foo = "bar".freeze
+foo.gsub!("bar", "car")
```

This raises;
``` ruby
FrozenError: can't modify frozen String
```

However, I would have expected this to work since +@ should return a duplicated mutable string.



-- 
https://bugs.ruby-lang.org/