Pre-1.0 Rust used to support writing code like:

match x {
    y @ z => { ... }
}

match a {
    b @ Some(c) => { ... }
}

PR #16053 disabled the ability to write such code. More precisely, it disabled the ability to introduce any kind of binding in subpattern P in the context of any binding-pattern ident @ P

The reason we did this was because it was too hard to h

Currently, a triple click will select the single complete line underneath the cursor. However, now that we have reflow, a single logical "line" can span many grid lines. A logical line is the content the text printed to the terminal thinks is a line, a grid line is a row in Alacritty's grid. Triple clicking today will miss parts of logical lines.

Other terminals (tested Termite and Urxvt) selec

I've been trying to export most of my dotfile-type configs to system packages I can install. A lot of programs offer the option for both a system and a user config (e.g. git reads from /etc/gitconfig, then ~/.gitconfig) although currently, bat reads just one file. It'd be nice if we could do something similar for bat as well, loading both /etc/bat/config and ~/.config/bat/config.

The member methods of CanvasState were largely extracted from CanvasRenderingContext2D, where they used to be members of the generated CanvasRenderContext2DMethods trait. Now that they are handwritten, it's confusing to have them keep the same naming pattern as generated code. We should rename them so GetImageData becomes get_image_data (for example).

We should also extract CanvasState into its

Here is some general documentation improvement suggestion regarding flatbuffers. This is what I remember struggling with (from the top of my head). Also some point might be a little bit opinionated.

Some of the points were taken from #5387.

• Regarding the builder:
  • The fact that its kinda like an arena allocator used for serialization.
  • The concept of offsets, what do they repre

For every scheme a fully running kernel has, the following functions need to be documented, if implemented. In addition, the Scheme and SchemeMut traits should be documented with usage and the default operation.

Documentation should include usage, what access restrictions there are, what paths and dup arguments are valid, and what errors may be returned.

Path Operations

• open

As discussed in this bat issue, the behavior of fd's -X flag is different from the behavior of fd | xargs. My initial impression upon reading the docs was that -X's behavior would be equivalent to piping to xargs, and I was surprised when that wasn't the case.

Shell session for reference:

$ for i in a b c d; do echo $i > $i.t

There's some confusion on how to properly use events here: yewstack/yew#152 I think better documentation would help

Thanks for the fantastic library!

I have been reading through documentation and examples to learn about Rocket. One thing that confused me is the use of macro_use, extern crate, and serde_derive, none of which I believe are necessary any more (or at least they do not appear to be in my testing). For example, the tera_template example currently begins with:

#[macro_use] extern 

Add a field on the breakpoint that shows the number of times a breakpoint was hit. See The -break-list Command.

Note: This is an issue that is in 0.1.x and in 0.2.x. Any fix should be backported.

UdpFramed violates the decode contract by not attempting to continue decoding past the first discrete item if there is more data in the buffer.

Correct Framed implementation https://github.com/tokio-rs/tokio/blob/v0.1.x/tokio-io/src/framed_read.rs#L199

and incorrect https://github.com/tokio-rs/tokio/blo

Consider https://gcc.godbolt.org/z/O4aVOC - this fails with a linker error: undefined reference to std::filesystem::__cxx11::directory_iterator::operator*() const'`

It was pointed out on discord that if the executable comes first, the link succeeds, i.e. this is a link order issue.

Specifically:

/opt/compiler-explorer/gcc-8.3.0/bin/g++ -g -o /tmp/output.s -masm=intel -fdiagnostics

• Parity Ethereum version: 2.4.5 or 2.4.6
• Operating system: Linux
• Installation: binary from Github | releases
• Fully synchronized: both, no and yes
• Network: ethereum
• Restarted: yes

Actual behaviour

When starting parity 2.4.5/2.4.6 in archive mode (tracing on, db_compaction ssd, pruning archive, fat_db on) with the default settings for the cache_size

After reading https://medium.com/@mlowicki/http-s-proxy-in-golang-in-less-than-100-lines-of-code-6a51c2f2c38c, the idea was born to write a proxy server on rust.

In https://github.com/hyperium/hyper/blob/master/examples/README.md is written that the example https://github.com/hyperium/hyper/blob/master/examples/upgrades.rs can help.

But I do not really understand how this can be done. I thin