Fixing "Confusing use of '!'" warning

[englishextra]

see [Incorrect "Confusing use of '!'" warning #780](here jshint/jshint#780)

[eligrey]

_ntoken and _nforce look a lot more confusing to me. Are people simply not allowed to use the negation operator now? _ntoken doesn't even describe what is represents. If I had to name a variable, I would name it token_not_found.

[englishextra]

@eligrey My code including polyfills come through travis-ci then pass jshint. So you know what I mean. You can offer another name for workaround variables. They are obviously for avoiding surpressing jshint comments.

[eligrey]

I don't do usually workarounds for bugs in third party tools and libraries that don't affect functionality. It's up to the third party to fix their issue.

This project now has new maintainers though so if they feel like this is necessary they may merge your PR.

[englishextra]

@eligrey

t's up to the third party to fix their issue.

That's right, and you aren't developing in vacuum, just for art.
Beck's aware of that issue already.

[eligrey]

@englishextra I would understand your concern if it impacted functionality, but it does not. JSHint being broken (has been for years for many types of expressions, I don't really use it anymore) doesn't mean the code will stop working or produce warnings to the end-user.

[englishextra]

@eligrey No problem

It all ends up that I have to relint every polyfill I use, and add .fixed suffix to the filename. I'm not happy with jshint and their stubbornness, likewise I'm not happy with xo as well.

So, it's up to new collaborators to merge that. Thanks.