Fix check_symbol_to_proc false positives on lambda literals

[kiyot]

Currently lambda literal like ->(x) { x.to_s } violates the check_symbol_to_proc rule.

This rule makes sense when it is applied to method calls with blocks, but I'm not sure if the violation on lambda literal is an intentional behavior.

It feels awkward to me if I have to write f = :to_s.to_proc instead of f = ->(x) { x.to_s }.

[DamirSvrtan]

Hey @kiyot, thanks for another great contribution! Please give me a bit of time to review this and understand it a bit more!

[DamirSvrtan]

Reviewed it and it makes sense to me, thanks for the contribution @kiyot!

[DamirSvrtan]

Now i just saw that our integration with Travis CI has not worked for some time - for me i'm getting failing specs on Ruby 2.6.1 - which version of Ruby are you running?

[kiyot]

I was using ruby 2.6.4, and one of the specs was failing.

[DamirSvrtan]

Alright, since they've been failing, i've reverted them. Do you mind opening another PR with specs passing?

[kiyot]

The spec had been failing even before my two PRs were merged.

[kiyot]

It looks like the failure is caused by the newest version of ruby_parser (3.14.0). When I use ruby_parser 3.13.0, all the specs pass.

[DamirSvrtan]

Thanks for clarifying, i've pinged the ruby_parser maintainers to let us know the supported versions of Ruby: seattlerb/ruby_parser#298.

Let's pickup this conversation after we resolve that!