cfg-if 1.0 is almost 2 years old at this point so I don't feel there is a reason to support pre-1.0 versions any longer. This change is meant to workaround a cargo bug where cargo will non-deterministically change the version back and forth between 0.1 and 1.0 if there is at least one more dependency on the 0.1 version, even for lockfile updates that don't directly touch cfg-if. Obviously this isn't critical, just a papercut.
cfg-if 1.0 is almost 2 years old at this point so I don't feel there is a reason to support pre-1.0 versions any longer. This change is meant to workaround a cargo bug where cargo will non-deterministically change the version back and forth between 0.1 and 1.0 if there is at least one more dependency on the 0.1 version, even for lockfile updates that don't directly touch cfg-if. Obviously this isn't critical, just a papercut.
Resolves: #85