Searched +full:ci +full:- +full:crate (Results 1 – 25 of 71) sorted by relevance
123
| /third_party/rust/crates/env_logger/.github/workflows/ |
| D | ci.yml | 6 - "**.rs"
7 - "Cargo.toml"
8 - "Cargo.lock"
13 runs-on: ubuntu-latest
15 - name: Checkout sources
18 - name: Install Rust toolchain
19 uses: actions-rs/toolchain@v1
26 - name: Check formatting
27 uses: actions-rs/cargo@v1
30 args: -- --check
[all …]
|
| /third_party/rust/crates/libc/ |
| D | CONTRIBUTING.md | 4 to the `libc` crate.
11 The internal structure of this crate is designed to minimize the number of
13 to all platforms in the future. As a result, the crate is organized
23 to `src/unix/mod.rs`, but when adding a Linux-only API it should be added to
27 at, fear not! This crate has CI support which tests any binding against all
32 symbols list(s) found in the `libc-test/semver` directory. These lists keep
33 track of what symbols are public in the libc crate and ensures they remain
34 available between changes to the crate. If the new symbol(s) are available on
43 4. Wait for CI to pass, fixing errors.
51 We have two automated tests running on [GitHub Actions](https://github.com/rust-lang/libc/actions):
[all …]
|
| D | README.md | 1 # libc - Raw FFI bindings to platforms' system libraries
3 [![GHA Status]][GitHub Actions] [![Cirrus CI Status]][Cirrus CI] [![Latest Version]][crates.io] [![…
6 code (or "C-like" code) on each of the platforms that Rust supports. This
10 This crate exports all underlying platform types, functions, and constants under
11 the crate root, so all items are accessible as `libc::foo`. The types and values
17 [rfc]: https://github.com/rust-lang/rfcs/blob/master/text/1291-promote-libc.md
37 * `const-extern-fn`: Changes some `extern fn`s into `const extern fn`s.
51 |----------------------|---------|
59 | `const-extern-fn` | 1.62.0 |
63 [Platform-specific documentation (master branch)][docs.master].
[all …]
|
| /third_party/rust/crates/shlex/ |
| D | README.md | 1 [![ci badge]][ci link] [![crates.io badge]][crates.io link] [![docs.rs badge]][docs.rs link]
3 [crates.io badge]: https://img.shields.io/crates/v/shlex.svg?style=flat-square
5 [docs.rs badge]: https://img.shields.io/badge/docs-online-dddddd.svg?style=flat-square
7 [ci badge]: https://img.shields.io/github/actions/workflow/status/comex/rust-shlex/test.yml?branch=…
8 [ci link]: https://github.com/comex/rust-shlex/actions
19 The algorithms in this crate are oblivious to UTF-8 high bytes, so they iterate
20 over the bytes directly as a micro-optimization.
22 Disabling the `std` feature (which is enabled by default) will allow the crate
23 to work in `no_std` environments, where the `alloc` crate, and a global
29 - Apache License, Version 2.0, ([LICENSE-APACHE](LICENSE-APACHE) or
[all …]
|
| /third_party/rust/crates/regex/regex-syntax/ |
| D | README.md | 1 regex-syntax
3 This crate provides a robust regular expression parser.
5 [](https://github.com/rus…
6 [](https://crates.io/crates/regex-syn…
7 [](https://github.com/rust…
12 https://docs.rs/regex-syntax
17 There are two primary types exported by this crate: `Ast` and `Hir`. The former
46 This crate has no `unsafe` code and sets `forbid(unsafe_code)`. While it's
47 possible this crate could use `unsafe` code in the future, the standard
48 for doing so is extremely high. In general, most code in this crate is not
[all …]
|
| /third_party/rust/crates/linux-raw-sys/ |
| D | README.md | 2 <h1><code>linux-raw-sys</code></h1>
9 …e/linux-raw-sys/actions?query=workflow%3ACI"><img src="https://github.com/sunfishcode/linux-raw-sy…
10 …alliance.zulipchat.com/#narrow/stream/206238-general"><img src="https://img.shields.io/badge/zulip…
11 …<a href="https://crates.io/crates/linux-raw-sys"><img src="https://img.shields.io/crates/v/linux-r…
12 …<a href="https://docs.rs/linux-raw-sys"><img src="https://docs.rs/linux-raw-sys/badge.svg" alt="do…
16 This crate contains bindgen-generated bindings for Linux's userspace API.
20 minimal type-safe, memory-safe, and I/O-safe API to the Linux system calls
21 built on these bindings, see the [rustix crate].
25 most things needed by general-purpose code.
27 To regenerate the generated bindings, run `cargo update && cd gen && cargo run --release`.
[all …]
|
| /third_party/rust/crates/is-terminal/ |
| D | README.md | 2 <h1><code>is-terminal</code></h1>
9 …code/is-terminal/actions?query=workflow%3ACI"><img src="https://github.com/sunfishcode/is-terminal…
10 …<a href="https://crates.io/crates/is-terminal"><img src="https://img.shields.io/crates/v/is-termin…
11 …<a href="https://docs.rs/is-terminal"><img src="https://docs.rs/is-terminal/badge.svg" alt="docs.r…
15 is-terminal is a simple utility that answers one question:
20 and may support color and other special features. This crate doesn't provide
23 On Unix-family platforms, this is effectively the same as the [`isatty`]
25 high-level stream types instead of raw file descriptors.
30 This crate is derived from [the atty crate] with [PR \#51] bug fix and
31 [PR \#54] port to windows-sys applied. The only additional difference is that
[all …]
|
| /third_party/rust/crates/proc-macro-error/ |
| D | README.md | 3 [](https://tra…
4 [](https://docs.rs/proc-macro-error)
5 …idden](https://img.shields.io/badge/unsafe-forbidden-success.svg)](https://github.com/rust-secure-…
7 This crate aims to make error reporting in proc-macros simple and easy to use.
8 Migrate from `panic!`-based errors for as little effort as possible!
10 Also, you can explicitly [append a dummy token stream][crate::dummy] to your errors.
12 To achieve his, this crate serves as a tiny shim around `proc_macro::Diagnostic` and
14 When the underlying diagnostic type is finally stabilized, this crate will be simply
17 So you can just use this crate and have *both* some of `proc_macro::Diagnostic` functionality
18 available on stable ahead of time and your error-reporting code future-proof.
[all …]
|
| /third_party/rust/crates/unicode-width/ |
| D | README.md | 1 # unicode-width
8 [](https://travis-ci.org/unicode…
10 [Documentation](https://unicode-rs.github.io/unicode-width/unicode_width/index.html)
13 extern crate unicode_width;
29 zero-width joiner and a microscope emoji.
32 extern crate unicode_width;
43 covered by this crate.
47 unicode-width does not depend on libstd, so it can be used in crates
57 unicode-width = "0.1.7"
|
| /third_party/rust/crates/static-assertions-rs/src/ |
| D | lib.rs | 1 …aw.githubusercontent.com/nvzqz/static-assertions-rs/assets/Banner.png)](https://github.com/nvzqz/s…
7 //! <a href="https://travis-ci.org/nvzqz/static-assertions-rs">
8 //! <img src="https://travis-ci.org/nvzqz/static-assertions-rs.svg?branch=master" alt="Buil…
10 //! <img src="https://img.shields.io/badge/rustc-^1.37.0-blue.svg" alt="rustc ^1.37.0">
16 //! _All_ checks provided by this crate are performed at [compile-time]. This
24 //! This crate is available [on crates.io][crate] and can be used by adding the
32 //! and this to your crate root (`main.rs` or `lib.rs`):
36 //! extern crate static_assertions;
44 //! extern crate static_assertions as sa;
56 //! See [`CHANGELOG.md`](https://github.com/nvzqz/static-assertions-rs/blob/master/CHANGELOG.md)
[all …]
|
| /third_party/rust/crates/clang-sys/ |
| D | README.md | 1 # clang-sys
3 [](https://crates.io/crates/clang-sys)
4 [](https://docs.rs/clang-sys)
5 [](https://github…
6 
10 …t idiomatic Rust wrapper for these bindings, see [`clang-rs`](https://github.com/KyleMayes/clang-r…
14 ## [Documentation](https://docs.rs/clang-sys)
16 Note that the documentation on https://docs.rs for this crate assumes usage of the `runtime` Cargo …
26 * `clang_3_5` - requires `libclang` 3.5 or later
27 * `clang_3_6` - requires `libclang` 3.6 or later
[all …]
|
| /third_party/rust/crates/codespan/ |
| D | CONTRIBUTING.md | 5 - [Introduction](#introduction)
6 - [Code of Conduct](#code-of-conduct)
7 - [Matrix Room](#matrix-room)
8 - [Reporting Bugs and Suggesting Improvements](#reporting-bugs-and-suggesting-improvements)
9 - [Contribution Workflow](#contribution-workflow)
10 - [Quality Standards](#quality-standards)
11 - [Release Process](#release-process)
30 Joining the matrix room at [#codespan:matrix.org][codespan-matrix] is a good way to get in touch wi…
32 [codespan-matrix]: https://app.element.io/#/room/#codespan:matrix.org
36 Bugs (unwanted behaviour) and suggested improvements are tracked as [GitHub issues][github-issues].
[all …]
|
| /third_party/rust/crates/libc/ci/ |
| D | README.md | 1 The goal of the libc crate is to have CI running everywhere to have the
3 result the CI is pretty complicated and also pretty large! Hopefully this can
7 Note that this documentation is quite outdated. See CI config and scripts
8 in the `ci` directory how we run CI now.
14 * `run-docker.sh` - a shell script run by most builders, it will execute
17 * `run.sh` - the actual script which runs tests for a particular architecture.
19 * `dox.sh` - build the documentation of the crate and publish it to gh-pages.
21 # CI Systems
23 Currently this repository leverages a combination of GitHub Actions and Cirrus CI
34 * Android runs in a [docker image][android-docker] with an emulator, the NDK,
[all …]
|
| /third_party/rust/crates/link-cplusplus/ |
| D | README.md | 1 `-lstdc++` or `-lc++`
4 …badge/github-dtolnay/link--cplusplus-8da0cb?style=for-the-badge&labelColor=555555&logo=github" hei…
5 ….shields.io/crates/v/link-cplusplus.svg?style=for-the-badge&color=fc8d62&logo=rust" height="20">](…
6 …elds.io/badge/docs.rs-link--cplusplus-66c2a5?style=for-the-badge&labelColor=555555&logo=docs.rs" h…
7 …orkflow/status/dtolnay/link-cplusplus/ci.yml?branch=master&style=for-the-badge" height="20">](http…
9 This crate exists for the purpose of passing `-lstdc++` or `-lc++` to the
13 Without this crate, a library would need to:
15 - pick one or the other to link, with no way for downstream applications to
17 - or link neither and require an explicit link flag provided by downstream
32 link-cplusplus = "1.0"
[all …]
|
| /third_party/rust/crates/memchr/ |
| D | README.md | 5 [](https://github.com/B…
8 Dual-licensed under MIT or the [UNLICENSE](https://unlicense.org/).
18 * The top-level module provides routines for searching for 1, 2 or 3 bytes
22 * The `memmem` sub-module provides forward and reverse substring search
26 is exactly what you want when searching either UTF-8 or arbitrary bytes.
31 `std` feature if you want to use it in a `#![no_std]` crate:
35 memchr = { version = "2", default-features = false }
44 `memchr` is a routine that is part of libc, although this crate does not use
49 available in this crate, then enabling the `libc` feature will use libc's
52 The rest of the functions in this crate, e.g., `memchr2` or `memrchr3` and the
[all …]
|
| /third_party/rust/crates/log/ |
| D | README.md | 6 …s](https://img.shields.io/github/workflow/status/rust-lang/log/CI/master)](https://github.com/rust…
15 crate, and the consumer of those libraries can choose the logging
23 This version is explicitly tested in CI and may be bumped in any release as needed. Maintaining com…
29 Libraries should link only to the `log` crate, and use the provided macros to
75 * [`systemd-journal-logger`](https://docs.rs/systemd-journal-logger/*/systemd_journal_logger/)
76 * [`slog-stdlog`](https://docs.rs/slog-stdlog/*/slog_stdlog/)
83 …* You may need to construct [an FFI-safe wrapper over `log`](https://github.com/rust-lang/log/issu…
92 The executable itself may use the `log` crate to log as well.
|
| /third_party/rust/crates/version_check/ |
| D | README.md | 3 [](https://gi…
7 This tiny crate checks that the running or installed `rustc` meets some version
9 `--version`. The path to the compiler is determined first via the `RUSTC`
18 [build-dependencies]
30 extern crate version_check as rustc;
33 println!("cargo:rustc-cfg=question_mark_operator");
37 Check that the running compiler was released on or after `2018-12-18`:
40 extern crate version_check as rustc;
42 match rustc::is_min_date("2018-12-18") {
52 extern crate version_check as rustc;
[all …]
|
| /third_party/rust/crates/lazycell/ |
| D | README.md | 6 …s://travis-ci.org/indiv0/lazycell" title="Travis Build Status"><img src="https://travis-ci.org/ind…
10 …" title="API Docs"><img src="https://img.shields.io/badge/API-docs-blue.svg" alt="api-docs-badge">…
11 …itle="Crates.io"><img src="https://img.shields.io/crates/v/lazycell.svg" alt="crates-io"></img></a>
12 …f="#license" title="License: MIT/Apache-2.0"><img src="https://img.shields.io/crates/l/lazycell.sv…
13 …coveralls.io/repos/github/indiv0/lazycell/badge.svg?branch=master" alt="coveralls-badge"></img></a>
39 extern crate lazycell;
42 See the [API docs][api-docs] for information on using the crate in your library.
55 for the project [crates.io][crates-io-repo].
65 See [LICENSE-APACHE][license-apache], and [LICENSE-MIT][license-mit] for details.
67 [api-docs]: https://indiv0.github.io/lazycell/lazycell
[all …]
|
| /third_party/rust/crates/libc/.github/ |
| D | PULL_REQUEST_TEMPLATE.md | 5 - \[ ] Edit corresponding file(s) under `libc-test/semver` when you add/remove item(s)
6 - \[ ] `rustc ci/style.rs && ./style src`
7 - \[ ] `cd libc-test && cargo test` (This might fail on your env due to environment difference betw…
8 - \[ ] Your PR that bumps up the crate version doesn't contain any other changes
|
| /third_party/rust/crates/clap/examples/ |
| D | cargo-example.md | 2 book](https://doc.rust-lang.org/cargo/reference/external-tools.html#custom-subcommands).
3 The crate [`clap-cargo`](https://github.com/crate-ci/clap-cargo) can help in
8 $ cargo-example --help
12 example A simple to use, efficient, and full-featured Command Line Argument Parser
16 -h, --help Print help
18 $ cargo-example example --help
19 A simple to use, efficient, and full-featured Command Line Argument Parser
24 --manifest-path <PATH>
25 -h, --help Print help
26 -V, --version Print version
[all …]
|
| D | cargo-example-derive.md | 2 book](https://doc.rust-lang.org/cargo/reference/external-tools.html#custom-subcommands).
3 The crate [`clap-cargo`](https://github.com/crate-ci/clap-cargo) can help in
8 $ cargo-example-derive --help
12 example-derive A simple to use, efficient, and full-featured Command Line Argument Parser
16 -h, --help Print help
18 $ cargo-example-derive example-derive --help
19 A simple to use, efficient, and full-featured Command Line Argument Parser
21 Usage: cargo example-derive [OPTIONS]
24 --manifest-path <MANIFEST_PATH>
25 -h, --help Print help
[all …]
|
| /third_party/rust/crates/proc-macro2/ |
| D | README.md | 1 # proc-macro2
3 …/badge/github-dtolnay/proc--macro2-8da0cb?style=for-the-badge&labelColor=555555&logo=github" heigh…
4 …g.shields.io/crates/v/proc-macro2.svg?style=for-the-badge&color=fc8d62&logo=rust" height="20">](ht…
5 …ields.io/badge/docs.rs-proc--macro2-66c2a5?style=for-the-badge&labelColor=555555&logo=docs.rs" hei…
6 …workflow/status/dtolnay/proc-macro2/ci.yml?branch=master&style=for-the-badge" height="20">](https:…
8 A wrapper around the procedural macro API of the compiler's `proc_macro` crate.
11 - **Bring proc-macro-like functionality to other contexts like build.rs and
14 `proc_macro2` types may exist anywhere including non-macro code. By developing
17 many other use cases and we avoid reimplementing non-macro equivalents of
20 - **Make procedural macros unit testable.** As a consequence of being specific
[all …]
|
| /third_party/rust/crates/rustix/ |
| D | README.md | 11 …src="https://github.com/bytecodealliance/rustix/workflows/CI/badge.svg" alt="Github Actions CI Sta…
12 …alliance.zulipchat.com/#narrow/stream/206238-general"><img src="https://img.shields.io/badge/zulip…
18 `rustix` provides efficient memory-safe and [I/O-safe] wrappers to POSIX-like,
19 Unix-like, Linux, and Winsock2 syscall-like APIs, with configurable backends.
21 [`io-lifetimes`] instead of raw file descriptors, providing memory safety,
27 `rustix` is low-level and, and while the `net` API supports Winsock2 on
28 Windows, the rest of the APIs do not support Windows; for higher-level and more
29 portable APIs built on this functionality, see the [`system-interface`],
30 [`cap-std`], and [`fs-set-times`] crates, for example.
35 supported on Linux on x86-64, x86, aarch64, riscv64gc, powerpc64le,
[all …]
|
| /third_party/rust/crates/termcolor/ |
| D | README.md | 6 are provided for use in single-threaded or multi-threaded command line
9 [](https://github.co…
12 Dual-licensed under MIT or the [UNLICENSE](https://unlicense.org/).
49 The `StandardStream` type in this crate works similarly to `std::io::Stdout`,
57 fn write_green() -> io::Result<()> {
76 fn write_green() -> io::Result<()> {
95 * In non-Windows environments, if `TERM` is not set, then colors will be
102 crate.
106 This crate's minimum supported `rustc` version is `1.34.0`.
108 The current policy is that the minimum Rust version required to use this crate
[all …]
|
| /third_party/rust/crates/strsim-rs/ |
| D | README.md | 1 # strsim-rs
4 …ields.io/crates/l/strsim.svg?maxAge=2592000)](https://github.com/dguo/strsim-rs/blob/master/LICENS…
5 [](https://github.com/dguo/st…
6 …idden](https://img.shields.io/badge/unsafe-forbidden-success.svg)](https://github.com/rust-secure-…
8 [Rust](https://www.rust-lang.org) implementations of [string similarity metrics]:
9 - [Hamming]
10 - [Levenshtein] - distance & normalized
11 - [Optimal string alignment]
12 - [Damerau-Levenshtein] - distance & normalized
13 …- [Jaro and Jaro-Winkler] - this implementation of Jaro-Winkler does not limit the common prefix l…
[all …]
|
123