non-exhaustive patterns: type &FileFormat is non-empty

[omid]

Hello,

After 0.12, when I disable default features, config fails with the following error.

For example, for this example, we don't need any feature to be enabled.

error[E0004]: non-exhaustive patterns: type `&FileFormat` is non-empty
   --> config-rs-753d70ca56f8adb9/7cf33db/src/file/format/mod.rs:101:15
    |
34  | / pub enum FileFormat {
35  | |     /// TOML (parsed with toml)
36  | |     #[cfg(feature = "toml")]
37  | |     Toml,
...   |
57  | |     Json5,
58  | | }
    | |_- `FileFormat` defined here
...
101 |           match self {
    |                 ^^^^
    |
    = help: ensure that all possible cases are being handled, possibly by adding wildcards or more match arms
    = note: the matched value is of type `&FileFormat`
    = note: references are always considered inhabited

For more information about this error, try `rustc --explain E0004`.

I think adding a _ => unreachable!() to the match can do the job.

[matthiasbeyer]

Hey, thanks for this good catch!