See rust-lang/rust#67755 (comment).

cc @rust-lang/wg-diagnostics

This issue has been assigned to @jumbatm via this comment.

When running Alacritty with the command alacritty --config-file /dev/null --print-events, events are initially printed, however after a config reload + events cleared event, no further winit events are logged.

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.

There's a big block of "generated" Rust code in CGClassConstructHook in CodegenRust.py which should be extracted into a helper method in a file like components/script/dom/bindings/utils.rs instead. Currently we end up with a lot of duplicated code in many files, and we could instead just generate a single call to the new helper method instead.

No need to run any tests; if the result compiles, t

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

As awesome-rust grows, there are a few tweaks that may improve readability, consistency, and load times. Before making changes en masse, it would be great to hear anyone's thoughts and a green light from maintainers.

• e.g current format (for half the current list. currently, not all entries include links to crates)
  • kbknapp/clap-rs [[clap](https://crat

This is similar to #333 which only addressed --exec-batch.

The docs that let you know how to build a custom rootfs and vmlinux are not complete in the idea that they do not show how to configure the VM after building both rootfs and vmlinux, and log in successfully inside the VM.

It would be nice to provide configuration for simple use cases like using a r

Description

I'm submitting a feature request:

Going along with #745, this would be a very nice usability improvement (as also mentioned in #756).

For example, this:

let placeholder = if something { "Something" } else { "Something else" };
let maxlength = if blah { 7 } else { 10 };
html! {
    <input type="text" /* ... */ placeholder=placeholder maxlength=maxlength 

The documentation of FromDataSimple doesn't mention that it's only for debugging. This is only mentioned at documentation of FromData.

Based on several closed issued about this and recent message at #beginners, this causes enough confusion that documentation of FromDataSimple should also mention this.

root@titanic /mnt/datastore/RAWs/.zfs# exa
".": Invalid argument (os error 22)
root@titanic /mnt/datastore/RAWs/.zfs# /bin/ls
snapshot

the ZFS file system creates a super-hidden (even ls -al wont show it) .zfs folder, but you can still cd into it. once in this folder, exa doesn't work. exa however works in sub-folders of .zfs, such as .zfs/snapshots. ls, as shown above, still works.

Is there a plan to add a CONTRIBUTING.md? This could include template to do a PR, guidelines to add tests, coding standards, etc.

I'm currently learning Rust and am very interested in contributing on this project somehow. Thanks!

Is it a suitable start for someone with 0 Rust experience? (my guess: yes, but it is a guess and it turned out to be wrong)

small exercises to get you used to reading and writing Rust code

indicates that it is for beginners, but it is unclear is it for someone just starting from hello world.

Alternatively, for a first-time Rust learner, there's several other resources:

Is it suppos

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

The panic messages when the reactor or timer are not available should be improved to better explain what a user needs to do to fix them (originally reported at hyperium/hyper#1995).

• Current timer panic: timer error: timer is shutdown
• Current reactor panic: no current reactor

Well, we need to check all the projects and remove outdated ones.

We declare this in the readme:

However, keep in mind that we don't accept mammoth's shit. Only active and interesting projects with good documentation are added. Dead and abandoned projects will be removed.

But, sadly at this moment, this project looks like a mammoth shit itself.

We really need to fix it. I think

Code Line: https://github.com/swc-project/swc/blob/master/ecmascript/parser/src/lexer/jsx.rs#L60

@kdy1

Full HTML escape characters support: LuoZijun/es@b67338f

Ref: HTML Character entity references

benchmark:

test lexer::htmlentity::bench_escape_html_with_bytes   ... ben

Question

I went to godbolt in the middle of the night and found it extremely bright and started wondering if it could respect the system setting.

There is a CSS media feature prefers-color-scheme which indicates whether the user prefers light or dark mode. It might be nice to make the default dark mode if the user hasn't explicitly picked one yet be "System" and using the prefers-color-scheme settin

We need documentation for the following Nu internal commands in any speaking language of your choosing:

If interest in working on a command, please read this first.

Please note: These are Nu commands, they may be the same name as commands you might be familiar from other shells but their usage, flags, and functionality migh

I recently introduced npm scripts to reliably get the correct tooling necessary to compile Citybound (see CONTRIBUTING.md). There are still some things that could be improved - I will try to do so whenever I find time for it, but if anyone wants to help earlier than that, I would really appreciate it.

• Make sure that npm run ensure-tooling installs correct rust nightly, rustfmt and clipp

• 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

The #[tokio::main] macro is used in most (all?) of the examples, and also shows up in documentation.

However, it's not a part of the hyper crate (and was explicitly removed from reexport hyperium/hyper#1878).

I feel like this could be a confusing spot for people new to hyper/tokio, perhaps it would

Feature Request

Is your feature request related to a problem? Please describe.

There is no documentation on how to update the prompt when a new release comes out

Describe the solution you'd like

Just a minor correction. You repeat the word to in the help that is printed as an answer to xsv cat -h:

... the result is always equivalent **to to** the minimum number of rows ...

There appears to be a lot of variation in how complete the "partially done" commands are. For example od seems fairly complete, but date doesn't even support simple usages like date +%Y%m%d, and sort seems to have a good selection of options, but is missing some relatively important ones like sort keys.

It would be really useful if there were some documentation clarifying how complete t

This issue is related to #51, windows support. When PR #175 lands, wasmer will have experimental support for windows! This is exciting, but does not mean work is finished. Wasmer will only be able to run simple programs that do not use Emscripten, so no nginx or lua. The reason is that the required syscalls have not been implemented for the Windows target.

There are stubs left for unimplemente