Oli Scherer

In order to enable travis, you'd need to activate this repository at `travis-ci.com` by logging in with github and finding the repo in your user-settings. You can see how this...

> Rust has unsigned types with a unary - operator that currently generate an error: https://doc.rust-lang.org/stable/reference.html#unary-operator-expressions. Looks like it will be fixed in rust-lang/rust#30538. I'm not fixing it. I'm making...

The span is inserted [here](https://github.com/rust-lang/rust/blob/289ad6e9922683807d455ca0020dc2a8f7bd1a7b/src/librustc_resolve/check_unused.rs#L148). It is originally taken from the `extern crate` item [here](https://github.com/rust-lang/rust/blob/4bb5d35659b6d8579007f49db09aa1d35782b834/src/librustc_resolve/build_reduced_graph.rs#L387). We'd probably just want to expand the span during the reporting though, so we could...

We could add a way to "rustfmt after fix" to ease this workflow. > This isn't intuitive to me at all, hence coming here with this issue. It never occurred...

Not technically security lints, but some of the MISRA-C lints apply to Rust, too. This is tracked in https://github.com/rust-lang/rust-clippy/issues/2227

> futures are one-time-use by design and this is not possible well, in a very pedantic way on could say that `Future + Serialize` bounds are possible, but only handwritten...

> But, I read a little bit on future's implementation with generators, and, it looks like this terrible crime may work: heh, yea, but this is easy to abuse for...

so... in essence: It would be best if we had language support for cloning async blocks/functions. I believe it should be doable, but I haven't read up on previous discussions...

Minimal step towards this: https://github.com/rust-lang/rust/issues/95360

There are multiple reasons the tokio runtime cannot be used: * the tokio runtime does not work on wasm * the tokio runtime uses threads macroquad is entirely single-threaded and...