Issue #12493 has been updated by Yuki Nishijima.

Status changed from Open to Third Party's Issue
Assignee set to Yuki Nishijima

I believe this issue has been fixed: https://github.com/yuki24/did_you_mean/commit/1c52c887c62b0921e799f94bcc4a846dc7cbc057

Could you try installing 1.0.2 of the `did_you_mean` gem and see if it fixes your issue?

```
$ gem i did_you_mean -v=1.0.2
$ ruby -e'test = some_string if (some_string = "test")'
```

----------------------------------------
Bug #12493: Confusing did_you_mean error
https://bugs.ruby-lang.org/issues/12493#change-59638

* Author: Guo Xiang Tan
* Status: Third Party's Issue
* Priority: Normal
* Assignee: Yuki Nishijima
* ruby -v: ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux]
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
```
 irb(main):001:0> test = some_string if (some_string = "test")
(irb):1: warning: found = in conditional, should be ==
NameError: undefined local variable or method `some_string' for main:Object
Did you mean?  some_string
	from (irb):1
	from /home/tgxworld/.rbenv/versions/2.3.1/bin/irb:11:in `<main>'
```

I think assignment in a one liner if statement isn't encouraged but I found the suggestion to be quite confusing. 



-- 
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>