Eric Huss

Hm, unfortunately I'm not able to reproduce that. Can you include a `.zip` file of a workspace the demonstrates the issue?

It should already be checking for `input` via the check on `e.target.nodeName`. Maybe attach a debugger and see why that isn't included?

@eminence I believe this is referring to [paths overrides](https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#paths-overrides), which are defined in `config.toml`. The package verification step still uses those overrides, when it probably shouldn't.

Thanks for the suggestion! However, this seems like a duplicate of https://github.com/rust-lang/mdBook/issues/919. I don't think making the webserver hookable is an approach I would want to take. The webserver is...

Hm, can you maybe post a video capture of what happens? I tried on iOS Firefox, but wasn't able to trigger any problems. Is this maybe on Android?

I'm trying to figure out, which reference rule rejects the following? ```rust static mut S: i32 = 1; const C: &mut i32 = unsafe { &mut S }; // ERROR:...

The cargo team discussed this and were largely in favor of at least initially adding a warning when using `--index` and the `publish` field contains an array. The message should...

Can you clarify what this issue means? What is "CMD+K support"?

Generally, though it is not fully documented, the productions are greedy in a sense that they will attempt to parse the longest possible set of tokens for a rule (even...

There is some documentation in https://github.com/rust-lang/cargo/blob/HEAD/src/doc/contrib/src/tests/writing.md that would need to be updated.