rust-lang/rust#43466

Also figure out where the docs belong when it stabilizes.

The implementation has diverged a bit from the original RFC (rust-lang/rfcs#1946). We should have some good docs on all the syntaxes supported.

cc @clarfon

The default bright colors are often indistinguishable from the normal colors. This impacts the functionality of the default configuration file, which should achieve to provide sensible defaults that are usable out of the box for most people.

Since colors are highly subjective, I'd propose that the best approach to take is to imitate the current behavior of the dim colors, by taking the normal c

Branching off from #573 - it would be very useful if bat automatically generated a sane, small, well commented config file for users.

For example:

• bat --config-file -o $file writes to $file
• bat --generate-config-file writes to the current default config location and prints the path

I assume the implementation would be a small static string or binary blog baked into the binary. N

It should be up to the embedder to decide what user agent to report in network requests, rather than deep in the engine in https://github.com/servo/servo/blob/8e0d037ee82da747fa9c13234d5c3677f930e690/components/config/opts.rs#L480 (and #25372 would have exacerbated this). We should add a method to the EmbedderMethods trait that returns the default user agent string, so that we can pass that to [th

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

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

Is it possible to add an option -prune, to not explore sub-directories, when the current directory has been matched ? (like find -prune)

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

The seccomp filters are tailored for the Firecracker musl build. We should specify how to run Firecracker when building it with gnu as well.

Requested by @rbrasga in firecracker-microvm/firecracker#1515 (comment)

Problem
It's possible that a developer retains a reference to a node ref that has been unmounted. To prevent the reference of an unmounted html element, Yew should be sure to clear the NodeRef when unmounting.

Suggested Fix

1. Set vtag's node ref to None in its VDiff::detach impl
2. Set vcomp's node ref to None in the DestroyComponent runnable

First of, thanks a lot for this very nice project :)

Documentation?

I have been playing quite a bit with rocket and have enjoyed all the very detailed examples listed here.
It appears though that they are not all following rustfmt convention.
I though it will be nice to apply formatting on those.

Thanks a lot !

CocoaPods is a dependency manager for Swift and Objective-C Cocoa projects. The Podfile is a specification that describes the dependencies of the targets of one or more Xcode projects. The file should simply be named Podfile.

Please add Podfile to the "Immediate" class.

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

Version

tokio v0.2.13

Documentation is currently published on a per-crate basis, which makes it difficult to find objects from the different crates. It's not always obvious which crate to search in, and newcomers may not be aware of the structure.

The docs at https://docs.rs/actix-web/2.0.0/actix_web currently look like this:

It would be really nice if it looked like this:

before

var _typeof = typeof _symbol2.default === "function" && typeof _iterator2.default === "symbol" ? function (obj) {
  return typeof obj;
} : function (obj) {
  return obj && typeof _symbol2.default === "function" && obj.constructor === _symbol2.default && obj !== _symbol2.default.prototype ? "symbol" : typeof obj;
};

after

var _typeof1 = typeof _symbol2.d

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

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

Feature Request

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

Currently, the “Secure Config” section contains information on how to report security issues. This may
be rather hard to find and should be more easily reachable from the main website. For
example, the “Community” drop-down could include a reference to the v

If yum isn't installed, for example, all snippets that start with yum should be hidden

1. this shouldn't impact startup time
2. if --show-all is used, there should be no filtering

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

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

Describe the solution you'd like
I'd like the source code to be automatically clang-formatted according to my settings anytime the code is compiled. That is, don't require me to use the contextual menu or keyboard shortcut to format the code. Just auto-format it; just like the code is auto-compiled too.

Well, ther

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

I'd like to use CONNECT method with HTTP (at least with 1.1, and, ideally with 2).

However, I don't think there's a way to unwrap the underlying stream from HTTP response.

Practically, I need an object that implements futures::io::AsyncRead and futures::io::AsyncWrite (from futures 0.3). Similar thing via tokio should work too.

Hello
i just recently found this game on rust-unofficial list. its seems there is no documentation for linux installation anywhere to be found. windows is easy cause they just use exe but for me linux i cant hardly know how to install it
i am using ubuntu 19.10 right now

See openethereum/openethereum#11542 (comment).

After we migrate all wiki to OpenEthereum org, we need to update all the links in README.md and CONTRIBUTING.md here.

As discussed in #1219

Implemented for wasi in #1229

unsafe requires manual verification that the function is being used correctly. In order to be able to manually verify, we must document which in invariants must be upheld. This is usually done in the # Safety section of a doc comment.

• Runtime core
• Runtime
• Clif backend
• LLVM backend
• Singlepass backe

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 ...