Matthew Woodcraft
Matthew Woodcraft
https://github.com/rust-lang/reference/pull/1194#issuecomment-1101856264 suggests documenting how `main()`s return value affects the process's exit status. I think the Reference doesn't currently have anything to say about what happens after `main()` returns. I suggest...
The Patterns chapter didn't say that struct patterns can match enum values, and didn't document how refutability works for enums.
Moves the descriptions of BOM removal, CRLF normalisation, and shebang removal to the "Input format" page. So the rest of the _Lexical structure_ chapter now assumes CRLF normalisation has already...
If I add a very long word to the index (8000 characters is enough on my machine), I get a stack overflow while serialising it. Here's how I was testing:...
`GPIO.split()` returns a `Parts` struct, whose members have types like `PIN0`: https://docs.rs/nrf51-hal/0.6.2/nrf51_hal/gpio/gpio/struct.Parts.html This means its members claim to implement the `embedded_hal::digital::InputPin` trait, and so the compiler will let you call...
`formality-check` isn't rejecting an is-implemented where clause with nonsense in the implementing type or in a parameter to the trait. For example it doesn't reject a where clause whose implementing...
I see the master branch now contains some of the new C++-style paragraph identifiers (strings like `[asm.rules.mem-same-as-ffi]`). I think it's important that the Reference's introduction should say something about what...
The following program is rejected: ````rust mod sub { fn prv() {} pub use prv as renamed; } ```` The restrictions which cause this rejection were introduced in [rfc136]. I...
The following program is rejected (though the `sub` module alone would be accepted with a warning): ````rust mod sub { struct Priv; pub fn get_value() -> Priv { todo!() }...
The "Type coercions" section says coercion is allowed from: - Function item types to fn pointers - Non capturing closures to fn pointers This ought to describe the compatibility requirements,...