Skip to content

Conversation

@schneems
Copy link
Collaborator

@schneems schneems commented Nov 3, 2021

I don't believe you can make a syntax error by missing a #{ in a string, if you do then you end up with no string embed:

"foo}" # => No syntax error
"#foo}" # => No syntax error
"{foo}" # => No syntax error

Removing this suggestion makes the error more clear. The default message will still be used which is essentially the same message minus the #{ part.

I don't believe you can make a syntax error by missing a `#{` in a string, if you do then you end up with no string embed:

```
"foo}" # => No syntax error
"#foo}" # => No syntax error
"{foo}" # => No syntax error
```

Removing this suggestion makes the error more clear. The default message will still be used which is essentially the same message minus the `#{` part.
@schneems schneems merged commit bfccfed into main Nov 3, 2021
@schneems schneems deleted the schneems/no-embed-string-message branch November 3, 2021 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants