disable LTO

[japaric]

to work around rustc issue 90357

[rockboynton]

this breaks rust-analyzer... it needs to not be a string:

lto = false

[Urhengulas]

@rockboynton With "breaks" you mean RA emits a warning, correct? Because it still works for me in the current form , it just underlines the "lto".

We can change that for sure. Do you want to send a patch? Nevertheless I am wondering if RA should also accept "false" and "true", because rustc does accept it.

Edit: the underlining comes from another extension, not RA

[Urhengulas]

Looking more into it, it seems that this results in an actual error in rust nightly, while it still works on stable.

$ cargo build --bins
   Compiling krate v0.1.0 (/home/urhengulas/Documents/github.com/knurling-rs/krate)
    Finished dev [optimized + debuginfo] target(s) in 0.16s

$ cargo +nightly build --bins
error: failed to parse manifest at `/home/urhengulas/Documents/github.com/knurling-rs/krate/Cargo.toml`

Caused by:
  `lto` setting of string `"false"` for `bench` profile is not a valid setting, must be a boolean (`true`/`false`) or a string (`"thin"`/`"fat"`/`"off"`) or omitted.