wont compile on nightly 2019-12-05

[toastmod]

Hey there I tried to run cargo +nightly-2019-12-05 install c2rust but I got this error
fyi I am on WSL Ubuntu 18.04.1 LTS

    |                          ^^
    |
    = note: for more information, see https://github.com/rust-lang/rust/issues/62254
    = help: add `#![feature(slice_patterns)]` to the crate attributes to enable

error[E0658]: subslice patterns are unstable
   --> /home/toast/.cargo/registry/src/github.com-1ecc6299db9ec823/object-0.23.0/src/read/mod.rs:194:26
    |
194 |             [0x4c, 0x01, ..]
    |                          ^^
    |
    = note: for more information, see https://github.com/rust-lang/rust/issues/62254
    = help: add `#![feature(slice_patterns)]` to the crate attributes to enable

error[E0658]: subslice patterns are unstable
   --> /home/toast/.cargo/registry/src/github.com-1ecc6299db9ec823/object-0.23.0/src/read/mod.rs:196:28
    |
196 |             | [0x64, 0x86, ..] => FileKind::Coff,
    |                            ^^
    |
    = note: for more information, see https://github.com/rust-lang/rust/issues/62254
    = help: add `#![feature(slice_patterns)]` to the crate attributes to enable

   Compiling hex v0.3.2
   Compiling unicode-segmentation v1.7.1
   Compiling hashbrown v0.9.1
   Compiling byteorder v1.4.2
   Compiling opener v0.4.1
   Compiling c2rust-refactor v0.15.0
   Compiling shell-escape v0.1.5
   Compiling either v1.6.1
   Compiling home v0.5.3
   Compiling hex v0.4.2
   Compiling bytesize v1.0.1
error: aborting due to 11 previous errors

For more information about this error, try `rustc --explain E0658`.
error: could not compile `object`.
warning: build failed, waiting for other jobs to finish...
error: failed to compile `c2rust v0.15.1`, intermediate artifacts can be found at `/tmp/cargo-installES3VcO`

[thedataking]

Possible duplicate of #323. Please try that workaround to confirm?

[toastmod]

Ah I really should have checked the other issues sorry. cargo +nightly-2019-12-05 install c2rust --locked worked great thanks.

[NoSharp]

@thedataking It might be a good Idea to pop this on the README, my apologies if this answer is already easily findable.