bumblingbear (Dillon Welch)
- Login: bumblingbear
- Registered on: 03/23/2018
- Last sign in: 03/09/2020
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 1 | 0 | 1 |
Activity
03/27/2018
-
04:17 AM Ruby Feature #14624: #{nil} allocates a fresh empty string each time
- Closer to the string interpolation optimization part. The problem with `"#{nil}"` is that it allocates two empty strings each time. I feel like it would be possible to do this with zero/one allocation. I don't know what the underlying co...
-
02:50 AM Ruby Feature #14624: #{nil} allocates a fresh empty string each time
- That sounds fine to me!
Hanmac (Hans Mackowiak) wrote:
> i have a problem with that, what if someone might do:
> ...
03/23/2018
-
03:49 AM Ruby Feature #14624 (Open): #{nil} allocates a fresh empty string each time
- This causes a bunch of unnecessary string allocations in the following scenario: `"#{'rails' unless boolean_condition} is great"`. Each time this line is called when `boolean_condition` is true, it evaluates to `nil` and when `nil` is in...