Frank Steffahn

Okay, wait… this is even worse. Every “auto merge” commit has the full PR message in it. Which means, if we look at _any_ PR that fixes an issues, e.g....

So… maybe the better approach is to somehow find-and-replace all non-prefixed issue numbers in the PR message when creating the commit message for the “auto merge” or the “rollup merge”...

Okay; even on older versions it still seems to work by means of writing ```rs pub trait TryStream: Stream { /// The type of successful values yielded by this future...

Nevermind, even that more explicit version doesn’t work before `1.46`; the `TryStream` trait may be older than that? _Edit:_ Yes it is.

…and I see a MSRV of `1.41` for futures if I’m interpreting that correctly. At least the comment should be updated to reflect that current Rust versions don’t have the...

Any progress here? This bug still exists and it’s regularly annoying me.

@calebcartwright (NB: I don’t fully understand the full status of the 2.0 branch, even after searching for it, because there doesn’t seem any good documentation of what it’s about.) I...

I see. Thank you for the explanation :-)

> If there are prompts (`>` or `$`) in the code blocks, they should use `console` Oh… I didn’t look close enough to notice that the `>` or `$` are...

Hi, this issue seems about related: I’m currently reading the online tutorial and on the generics page, https://eta-lang.org/docs/eta-concepts/java-interop/java-generics, under “Working With Java Generics”, the import syntax on the top of...