unit: use ContainsAny instead of IndexAny

[muesli]

Caution: If I'm not mistaken ContainsAny wasn't available before Go 1.5. I'm not sure which minimum Go version go-systemd is aiming for, but if it's still <1.5 then you might not want to merge this PR.

That being said, I think it reads nicer.

Edit: I was mistaken, bytes.ContainsAny was introduced with the 1.7 release.

[lucab]

I have a minimum Go version bump (to >=1.10) on my roadmap, but I'm waiting for at least Go 1.11 to be released before doing that. I think I'm going to merge this PR at that later point. Bumping will also require some Travis adjustment.

For the moment, I'll keep this open and wait. In general it looks good, thanks a lot!

[lucab]

@muesli I just merged #278 which should make testing against specific go versions easier. Feel free to rebase this PR on master and adjust the minimum go version as needed.

[muesli]

@lucab Will do!

[muesli]

Pushed. This would bump the minimum required Go version to 1.7.

I'm not sure it's worth bumping the requirement for this change alone, though, to be honest. That being said, 1.7 also came with context, which would probably open up the door for some other nice changes in go-systemd.

Happy to keep this alive until we eventually decide to bump the requirement.

[lucab]

Ack, I'll keep this around open. We can queue it anytime in the future when we will need to bump the toolchain.

[lucab]

@muesli mind rebasing on current master? Minimum toolchain just bumped to 1.7 due to go-dbus anyway.

[muesli]

Will do in a minute!

[muesli]

@lucab Good to go from my POV.

[muesli]

The one failed Travis job looks like a fluke / unlikely name clash to me?

Edit: I'll force push to my branch to test that theory...

[lucab]

Yes, it's a known flake: #290

I re-triggered and it's green now, merging. Thanks a lot (with some delay 😄)!