Fix warnings

[dsander]

Fixes two ruby warnings:

warning: instance variable @something not initialized

and

assigned but unused variable something

[coveralls]

Coverage decreased (-0.3%) to 95.033% when pulling 225ee99 on dsander:fix-warnings into 077dc9d on xeger:master.

[xeger]

Good work; thank you. It looks like the warnings are only emitted during RSpec runs, hence, no need to publish a new version. Correct?

[dsander]

Thanks for creating the gem! I noticed the errors when I ran specs which used backticks. Even though it used the same RSpec version I did not even need to explicitly enable warnings, not sure why that was required in the specs here.
I guess one would also get the warnings if a one enables warnings for ruby in general. I am good with having a monkey match for now 😄

[xeger]

Okay; let me know if it becomes annoying and I'll release a new patchlevel to RubyGems.

…

On Mon, Oct 16, 2017 at 11:07 AM Dominik Sander ***@***.***> wrote: Thanks for creating the gem! I noticed the errors when I ran specs which used backticks. Even though it used the same RSpec version I did not even need to explicitly enable warnings, not sure why that was required in the specs here. I guess one would also get the warnings if a one enables warnings for ruby in general. I am good with having a monkey match for now 😄 — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#14 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEemCQjPstvDBAQdqAaICHEmw8T2SAiks5ss5tfgaJpZM4P4nli> .

[xeger]

FYI @dsander, I published v1.0.2 with your fixes.

[dsander]

Thank you!