1# Reporting region errors
2
3▶TODO: we should discuss how to generate errors from the results of these analyses.
4
128 matches across 25 files for TODO lang:Markdown
1# Inline Assembly
2
3▶**TODO**: You can find more info
4[here](https://github.com/rust-lang/rust/pull/69171#issue-375572066)
5[#1162](https://github.com/rust-lang/rustc-dev-guide/issues/1162)
13`-Z unpretty=expanded,identified` flag may be useful.
14
15▶TODO: anything else? [#1159](https://github.com/rust-lang/rustc-dev-guide/issues/1159)
16
17
18> _Note:_ The Clippy CI should also be described in this chapter, but for now is
19▶> left as a TODO.
20
35[^restrict]: Some use cases for `restriction` lints include:
36 - Strict coding styles (e.g. [`clippy::else_if_without_else`]).
37▶ - Additional restrictions on CI (e.g. [`clippy::todo`]).
38 - Preventing panicking in certain functions (e.g. [`clippy::unwrap_used`]).
39 - Running a lint only on a subset of code (e.g. `#[forbid(clippy::float_arithmetic)]` on a module).
· · ·
40
41[`clippy::else_if_without_else`]: https://rust-lang.github.io/rust-clippy/master/index.html#else_if_without_else
42▶[`clippy::todo`]: https://rust-lang.github.io/rust-clippy/master/index.html#todo
43[`clippy::unwrap_used`]: https://rust-lang.github.io/rust-clippy/master/index.html#unwrap_used
44
5This is a template for [stabilization reports](./stabilization-guide.md) of **language features**. The questions aim to solicit the details most often needed. These details help reviewers to identify potential problems upfront. Not all parts of the template will apply to every stabilization. If a question doesn't apply, explain briefly why.
6
7▶Copy everything after the separator and edit it as Markdown. Replace each *TODO* with your answer.
8
9---
· · ·
22> - [Stabilize opaque type precise capturing](https://web.archive.org/web/20250312173538/https://github.com/rust-lang/rust/pull/127672)
23
24▶*TODO*
25
26Tracking:
· · ·
27
28▶- *TODO* (Link to tracking issue.)
29
30Reference PRs:
· · ·
31
32▶- *TODO* (Link to Reference PRs.)
33
34cc @rust-lang/lang @rust-lang/lang-advisors
· · ·
39
40```rust
41▶todo!()
42```
43
+ 49 more matches in this file
115which are effectively tests for a single variant.
116
117▶### Use "TODO" comments for things you don't want to forget
118
119As a useful tool to yourself, you can insert a `// TODO` comment
· · ·
119▶As a useful tool to yourself, you can insert a `// TODO` comment
120for something that you want to get back to before you land your PR:
121
· · ·
123fn do_something() {
124 if something_else {
125▶ unimplemented!(); // TODO write this
126 }
127}
· · ·
128```
129
130▶The tidy script will report an error for a `// TODO` comment, so this
131code would not be able to land until the TODO is fixed (or removed).
132
· · ·
131▶code would not be able to land until the TODO is fixed (or removed).
132
133This can also be useful in a PR as a way to signal from one commit that you are
+ 1 more matches in this file
56rustc.main.000-000.CleanEndRegions.after.mir rustc.main.000-000.CleanEndRegions.before.mir
57```
58▶<!--- TODO: Change NoLandingPads. [#1232](https://github.com/rust-lang/rustc-dev-guide/issues/1232) -->
59Filters can also have `|` parts to combine multiple sets of
60`&`-filters. For example `main & CleanEndRegions | main &
· · ·
89
90
91▶TODO: anything else?
92
93[dataflow state]: ./dataflow.html#graphviz-diagrams
48 *move path* concept that we use to track which local variables (or parts of
49 local variables, in some cases) are initialized.
50▶- TODO *Rest not yet written* =)
51
44[collect]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_hir_analysis/collect/index.html
45
46▶**TODO**: actually talk about type checking... [#1161](https://github.com/rust-lang/rustc-dev-guide/issues/1161)
47
94* `ignore-tidy-dbg`
95* `ignore-tidy-odd-backticks`
96▶* `ignore-tidy-todo`
97
98Some checks, like `alphabetical`, require a tidy directive to use:
· · ·
104// tidy-alphabetical-end
105```
106▶<!--ignore-tidy-todo-->While not exactly a tidy directive, // TODO will fail tidy and make sure you can't merge a PR with unfinished work.
107
108### Test Specific Directives
1# Specialization
2
3▶**TODO**: where does Chalk fit in? Should we mention/discuss it here?
4
5Defined in the `specialize` module.
129use clippy_utils::ty::implements_trait;
130
131▶let ty = todo!("Get the `Foo` type to check for a trait implementation");
132let borrow_id = cx.tcx.get_diagnostic_item(sym::Borrow).unwrap(); // avoid unwrap in real code
133let slice_of_bytes_t = Ty::new_slice(cx.tcx, cx.tcx.types.u8);
· · ·
134let generic_param = slice_of_bytes_t.into();
135if implements_trait(cx, ty, borrow_id, &[generic_param]) {
136▶ todo!("Rest of lint implementation")
137}
138```
32[^restrict]: Some use cases for `restriction` lints include:
33 - Strict coding styles (e.g. [`clippy::else_if_without_else`]).
34▶ - Additional restrictions on CI (e.g. [`clippy::todo`]).
35 - Preventing panicking in certain functions (e.g. [`clippy::unwrap_used`]).
36 - Running a lint only on a subset of code (e.g. `#[forbid(clippy::float_arithmetic)]` on a module).
· · ·
37
38[`clippy::else_if_without_else`]: https://rust-lang.github.io/rust-clippy/master/index.html#else_if_without_else
39▶[`clippy::todo`]: https://rust-lang.github.io/rust-clippy/master/index.html#todo
40[`clippy::unwrap_used`]: https://rust-lang.github.io/rust-clippy/master/index.html#unwrap_used
41
59(~95% when compiling rustc).
60
61▶**TODO**: it looks like `pick_candidate_cache` no longer exists. In
62general, is this section still accurate at all?
63
55[ssamir]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_codegen_ssa/mir/index.html
56
57▶> TODO: discuss how constants are generated
58
8the program.
9
10▶TODO -- elaborate further? Maybe? :)
11
12## User types
41We then apply them in while borrow-checking its parent in `TypeChecker::prove_closure_bounds`.
42
43▶TODO: explain how exactly that works :3
44
123 trace!(?run, "entered Foo::should_run");
124
125▶ todo!()
126 }
127
· · ·
129 trace!(?run, "entered Foo::run");
130
131▶ todo!()
132 }
133}
71## How exactly does canonicalization work
72
73▶TODO: link to code once the PR lands and elaborate
74
75- types and consts: infer to existentially bound var, placeholder to universally bound var,
18This makes sure there are no dangling [`Id`]s.
19
20▶<!-- TODO: It does some more things too?
21Also, talk about how it works
22 -->
84'static}`, which fails the leak check.
85
86▶**TODO**: This is because `'static` is not a region variable but is in the
87taint set, right?
88
65the moment.
66
67▶TODO: write about _how_ these regions are computed.
68
69[`UniversalRegions`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_borrowck/universal_regions/struct.UniversalRegions.html
· · ·
223[`closure_bounds_mapping`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_borrowck/region_infer/struct.RegionInferenceContext.html#structfield.closure_bounds_mapping
224
225▶TODO: should we discuss any of the others fields? What about the SCCs?
226
227Ok, now that we have constructed a `RegionInferenceContext`, we can do
420 - `AST` definition: [`rustc_ast`](https://doc.rust-lang.org/nightly/nightly-rustc/rustc_ast/ast/index.html)
421 - Feature gating: [Feature Gate Checking](feature-gate-check.md)
422▶ - Early linting: **TODO**
423- The High Level Intermediate Representation (HIR)
424 - Guide: [The HIR](hir.md)
· · ·
428 - How to view `HIR` representation for your code `cargo rustc -- -Z unpretty=hir-tree`
429 - Rustc `HIR` definition: [`rustc_hir`](https://doc.rust-lang.org/nightly/nightly-rustc/rustc_hir/index.html)
430▶ - Main entry point: **TODO**
431 - Late linting: **TODO**
432- Type Inference
· · ·
431▶ - Late linting: **TODO**
432- Type Inference
433 - Guide: [Type Inference](type-inference.md)
· · ·
450- Code Generation
451 - Guide: [Code Generation](backend/codegen.md)
452▶ - Generating Machine Code from `LLVM-IR` with LLVM - **TODO: reference?**
453 - Main entry point: [`rustc_codegen_ssa::base::codegen_crate`](https://doc.rust-lang.org/nightly/nightly-rustc/rustc_codegen_ssa/base/fn.codegen_crate.html)
454 - This monomorphizes and produces `LLVM-IR` for one codegen unit.
431}
432
433▶fn bar<'b, T: Trait<'b>>() -> T::Assoc { todo!() }
434fn foo<'a>()
435where
· · ·
493 fn foo() -> IsEqual<Self, Self::Assoc> {
494 //~^ ERROR the trait bound `Self: Eq<<Self as Trait>::Assoc>` is not satisfied
495▶ todo!()
496 }
497}
Search syntax
auth login | both terms (AND is implicit) |
auth OR login | either term |
NOT path:vendor | exclude matches |
"exact phrase" | quoted exact match |
/func\s+Test/ | regex |
handler~1 | fuzzy (Levenshtein 1) |
file:*_test.go | filename glob |
path:pkg/auth/** | full path glob |
lang:go | language filter |