| /third_party/gn/src/gn/ |
| D | rust_project_writer.cc | 183 std::string_view crate, in AddSysrootCrate() argument
187 if (sysroot_crate_lookup.find(crate) != sysroot_crate_lookup.end()) { in AddSysrootCrate()
193 auto deps_lookup = sysroot_deps_map.find(crate); in AddSysrootCrate()
203 sysroot_crate_lookup.insert(std::make_pair(crate, crate_index)); in AddSysrootCrate()
209 "/lib/rustlib/src/rust/library/" + std::string(crate) + "/src/lib.rs"; in AddSysrootCrate()
212 std::string(crate), "2018"); in AddSysrootCrate()
238 for (auto crate : sysroot_crates) { in AddSysroot() local
239 AddSysrootCrate(build_settings, crate, sysroot, sysroot_lookup[sysroot], in AddSysroot()
244 void AddSysrootDependencyToCrate(Crate* crate, in AddSysrootDependencyToCrate() argument
249 crate->AddDependency(crate_idx->second, std::string(crate_name)); in AddSysrootDependencyToCrate()
[all …]
|
| D | rust_variables.cc | 30 This target would compile the `foo` crate with the following `extern` flag:
47 "crate_name: [string] The name for the compiled crate.";
49 R"(crate_name: [string] The name for the compiled crate.
67 This field sets the `crate-type` attribute for the `rustc` tool on static
70 crate type (where the Rust compiler produces what it thinks is the
73 It should be noted that the "dylib" crate type in Rust is unstable in the set
|
| /third_party/rust/crates/cxx/book/src/build/ |
| D | cargo.md | 11 CXX's integration with Cargo is handled through the [cxx-build] crate.
30 [`cc::Build`] instance (from the usual widely used `cc` crate) on which you can
61 With cxx-build, by default your include paths always start with the crate name.
65 Your crate name is determined by the `name` entry in Cargo.toml.
67 For example if your crate is named `yourcratename` and contains a C++ header
74 A crate can choose a prefix for its headers that is different from the crate
99 have `#include "path/to/header.h"`. However, if your crate is a library, be
102 within the crate is sufficiently namespaced or unique.
128 It works the same as an include of a local header: use the crate name (or their
129 include\_prefix if their crate changed it) followed by the relative path of the
[all …]
|
| /third_party/rust/crates/cxx/tests/ui/ |
| D | nonlocal_rust_type.stderr | 1 …r[E0117]: only traits defined in the current crate can be implemented for types defined outside of…
7 | | `Option` is not defined in the current crate
8 | impl doesn't use only types from inside the current crate
12 …r[E0117]: only traits defined in the current crate can be implemented for types defined outside of…
18 | | `Option` is not defined in the current crate
19 | impl doesn't use only types from inside the current crate
|
| /third_party/typescript/tests/baselines/reference/ |
| D | typeGuardFunctionOfFormThis.types | 231 let crate: Crate<{}>;
232 >crate : Crate<{}>
234 if (crate.isSundries()) {
235 >crate.isSundries() : boolean
236 >crate.isSundries : () => this is Crate<Sundries>
237 >crate : Crate<{}>
240 crate.contents.broken = true;
241 >crate.contents.broken = true : true
242 >crate.contents.broken : boolean
243 >crate.contents : Sundries
[all …]
|
| D | typeGuardFunctionOfFormThis.js | 100 let crate: Crate<{}>; variable
102 if (crate.isSundries()) {
103 crate.contents.broken = true;
105 else if (crate.isSupplies()) {
106 crate.contents.spoiled = true;
257 var crate; variable
258 if (crate.isSundries()) {
259 crate.contents.broken = true;
261 else if (crate.isSupplies()) {
262 crate.contents.spoiled = true;
[all …]
|
| D | typeGuardFunctionOfFormThis.symbols | 229 let crate: Crate<{}>;
230 >crate : Symbol(crate, Decl(typeGuardFunctionOfFormThis.ts, 98, 3))
233 if (crate.isSundries()) {
234 >crate.isSundries : Symbol(Crate.isSundries, Decl(typeGuardFunctionOfFormThis.ts, 94, 42))
235 >crate : Symbol(crate, Decl(typeGuardFunctionOfFormThis.ts, 98, 3))
238 crate.contents.broken = true;
239 >crate.contents.broken : Symbol(Sundries.broken, Decl(typeGuardFunctionOfFormThis.ts, 87, 20))
240 >crate.contents : Symbol(Crate.contents, Decl(typeGuardFunctionOfFormThis.ts, 91, 20))
241 >crate : Symbol(crate, Decl(typeGuardFunctionOfFormThis.ts, 98, 3))
245 else if (crate.isSupplies()) {
[all …]
|
| /third_party/gn/examples/rust_example/build/ |
| D | BUILD.gn | 5 …command = "rustc --crate-name {{crate_name}} {{source}} --crate-type {{crate_type}} --emit=dep-inf…
13 …command = "rustc --crate-name {{crate_name}} {{source}} --crate-type {{crate_type}} --emit=dep-inf…
21 …command = "rustc --crate-name {{crate_name}} {{source}} --crate-type {{crate_type}} --emit=dep-inf…
29 …command = "rustc --crate-name {{crate_name}} {{source}} --crate-type {{crate_type}} --emit=dep-inf…
|
| /third_party/rust/crates/regex/regex-syntax/ |
| D | README.md | 3 This crate provides a robust regular expression parser.
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
53 The standard for using `unsafe` in this crate is extremely high because this
54 crate is intended to be reasonably safe to use with user supplied regular
63 By default, this crate bundles a fairly large amount of Unicode data tables
70 [in the "Crate features" section of the documentation](https://docs.rs/regex-syntax/*/#crate-featur…
76 of the large number of features exposed by this crate, a `test` script is
[all …]
|
| /third_party/rust/crates/memchr/ |
| D | README.md | 31 `std` feature if you want to use it in a `#![no_std]` crate:
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
53 substring search routines, will always use the implementations in this crate.
61 This crate's minimum supported `rustc` version is `1.41.1`.
63 The current policy is that the minimum Rust version required to use this crate
64 can be increased in minor version updates. For example, if `crate 1.0` requires
65 Rust 1.20.0, then `crate 1.0.z` for all values of `z` will also require Rust
66 1.20.0 or newer. However, `crate 1.y` for `y > 0` may require a newer minimum
[all …]
|
| /third_party/rust/crates/pin-project-lite/tests/ui/pin_project/ |
| D | invalid-bounds.stderr | 27 …= note: this error originates in the macro `$crate::__pin_project_parse_generics` (in Nightly buil…
42 …= note: this error originates in the macro `$crate::__pin_project_parse_generics` (in Nightly buil…
58 …= note: this error originates in the macro `$crate::__pin_project_parse_generics` (in Nightly buil…
74 …= note: this error originates in the macro `$crate::__pin_project_parse_generics` (in Nightly buil…
90 …= note: this error originates in the macro `$crate::__pin_project_parse_generics` (in Nightly buil…
105 …= note: this error originates in the macro `$crate::__pin_project_parse_generics` (in Nightly buil…
121 …= note: this error originates in the macro `$crate::__pin_project_parse_generics` (in Nightly buil…
137 …= note: this error originates in the macro `$crate::__pin_project_parse_generics` (in Nightly buil…
153 …= note: this error originates in the macro `$crate::__pin_project_parse_generics` (in Nightly buil…
168 …= note: this error originates in the macro `$crate::__pin_project_parse_generics` (in Nightly buil…
[all …]
|
| D | unsupported.stderr | 9 …= note: this error originates in the macro `$crate::__pin_project_expand` (in Nightly builds, run …
19 …= note: this error originates in the macro `$crate::__pin_project_expand` (in Nightly builds, run …
43 …= note: this error originates in the macro `$crate::__pin_project_expand` (in Nightly builds, run …
55 …= note: this error originates in the macro `$crate::__pin_project_expand` (in Nightly builds, run …
67 …= note: this error originates in the macro `$crate::__pin_project_expand` (in Nightly builds, run …
79 …= note: this error originates in the macro `$crate::__pin_project_expand` (in Nightly builds, run …
|
| /third_party/rust/crates/termcolor/wincolor/ |
| D | README.md | 1 ## **This crate has reached its end-of-life and is now deprecated.**
3 This crate was rolled into the
5 crate since `wincolor` is quite small and didn't otherwise have a good reason
6 for living life as a distinct crate.
15 The purpose of this crate is to expose the full inflexibility of the Windows
35 and this to your crate root:
38 extern crate wincolor;
|
| /third_party/rust/crates/is-terminal/ |
| D | README.md | 20 and may support color and other special features. This crate doesn't provide
30 This crate is derived from [the atty crate] with [PR \#51] bug fix and
32 the atty crate only accepts stdin, stdout, or stderr, while this crate accepts
33 any stream. In particular, this crate does not access any stream that is not
96 This crate currently works on the version of [Rust on Debian stable], which is
99 version of this crate.
102 [the atty crate]: https://crates.io/crates/atty
|
| /third_party/typescript/tests/cases/conformance/expressions/typeGuards/ |
| D | typeGuardFunctionOfFormThis.ts | 100 let crate: Crate<{}>; variable
102 if (crate.isSundries()) {
103 crate.contents.broken = true;
105 else if (crate.isSupplies()) {
106 crate.contents.spoiled = true;
|
| /third_party/rust/crates/link-cplusplus/ |
| D | README.md | 9 This crate exists for the purpose of passing `-lstdc++` or `-lc++` to the
13 Without this crate, a library would need to:
47 flags from its build script can make this crate do nothing by using:
54 Lastly, make sure to add an explicit `extern crate` dependency to your crate
55 root, since the link-cplusplus crate will be otherwise unused and its link flags
61 extern crate link_cplusplus;
|
| /third_party/rust/crates/lazy-static.rs/compiletest/tests/compile-fail/ |
| D | README.md | 4 For more information check out [`compiletest` crate](https://github.com/laumann/compiletest-rs).
8 ## Notes on working with `compiletest` crate
11 crate cannot deal with the fact that macro invocations effectively changes
15 * `compiletest` crate by default sets `allow(dead_code)` lint level so make sure
20 issue in the `compiletest` crate and your error was probably not registered -
|
| /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
27 at, fear not! This crate has CI support which tests any binding against all
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
63 `libc` crate successfully. It's annoying to do the equivalent of semver-major versioning
77 When Rust removes a support for a target, the libc crate also may remove the support anytime.
82 platform in this crate, the next step is to get that sweet, sweet usage from
90 1. Once merged, the release will be tagged and published by one of the libc crate
|
| /third_party/rust/crates/codespan/codespan/ |
| D | README.md | 4 [![Crates.io][crate-badge]][crate-url]
10 [crate-url]: https://crates.io/crates/codespan
11 [crate-badge]: https://img.shields.io/crates/v/codespan.svg
|
| /third_party/rust/crates/cxx/third-party/ |
| D | BUCK | 11 crate = "bitflags",
36 crate = "cc",
127 crate = "clap",
147 crate = "clap_lex",
172 crate = "codespan_reporting",
198 crate = "once_cell",
230 crate = "os_str_bytes",
256 crate = "proc_macro2",
275 crate = "build_script_build",
317 crate = "quote",
[all …]
|
| /third_party/rust/crates/linux-raw-sys/ |
| D | README.md | 16 This crate contains bindgen-generated bindings for Linux's userspace API.
21 built on these bindings, see the [rustix crate].
32 rather than in a build.rs, making downstream builds simpler. And, this crate
38 This crate currently works on the version of [Rust on Debian stable], which is
41 version of this crate.
44 [rustix crate]: https://github.com/bytecodealliance/rustix#linux-raw-syscall-support
|
| /third_party/rust/crates/unicode-ident/ |
| D | README.md | 14 This crate is a better optimized implementation of the older `unicode-xid`
15 crate. This crate uses less static storage, and is able to classify both ASCII
26 - `unicode-ident` is this crate;
27 - [`unicode-xid`] is a widely used crate run by the "unicode-rs" org;
32 crate bakes into your binary, measured in 1000s of bytes.
87 Overall, the crate ends up being about 10× slower on non-ASCII input
88 compared to the fastest crate.
138 One possible performance improvement would be for this crate to expose a way to
163 This crate is a pure-Rust implementation of [Roaring Bitmap], a data structure
177 I also benchmarked the [`croaring`] crate which is an FFI wrapper around the C
[all …]
|
| /third_party/rust/crates/termcolor/ |
| D | README.md | 49 The `StandardStream` type in this crate works similarly to `std::io::Stdout`,
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
109 can be increased in minor version updates. For example, if `crate 1.0` requires
110 Rust 1.20.0, then `crate 1.0.z` for all values of `z` will also require Rust
111 1.20.0 or newer. However, `crate 1.y` for `y > 0` may require a newer minimum
114 In general, this crate will be conservative with respect to the minimum
|
| /third_party/rust/crates/regex/ |
| D | README.md | 26 To bring this crate into your repository, either add `regex` to your
93 [`lazy_static`](https://crates.io/crates/lazy_static) crate to ensure that
114 The main API of this crate (`regex::Regex`) requires the caller to pass a
182 This repository contains a crate that provides a well tested regular expression
194 This crate comes with several features that permit tweaking the trade off
196 crate can selectively disable Unicode tables, or choose from a variety of
197 optimizations performed by this crate to disable.
212 This will reduce the dependency tree of `regex` down to a single crate
216 [in the "Crate features" section of the documentation](https://docs.rs/regex/*/#crate-features).
221 This crate's minimum supported `rustc` version is `1.41.1`.
[all …]
|
| /third_party/rust/crates/tracing/ |
| D | CONTRIBUTING.md | 38 have uncovered a bug in a Tracing crate, creating a new issue in the
126 example), it is either adding new functionality to a crate or it is fixing
128 include one or more tests to ensure that the crate does not regress in the future.
134 Integration tests go in the same crate as the code they are testing. Each sub
135 crate should have a `dev-dependency` on `tracing` itself. This makes all
136 `tracing` utilities available to use in tests, no matter the crate being
140 integration tests in the crate and follow the style.
249 * be prefixed with the name of the crate being changed (without the
405 When releasing a new version of a crate, follow these steps:
407 1. **Ensure that the release crate has no path dependencies.** When the HEAD
[all …]
|