← Repo overview
/
rust-lang/ rust/
search
@e95e732
128 matches across 25 files for TODO lang:Markdown
snippet_mode: grep · sorted by relevance
6001 ```markdown
6002 - [x] Complete
6003 ▶ - [ ] Todo
6004 ```
6005
· · ·
7747 - [`mem::take`]
7748 - [`slice::repeat`]
7749 ▶ - [`todo!`]
7750
7751 Cargo
· · ·
7812 [`mem::take`]: https://doc.rust-lang.org/std/mem/fn.take.html
7813 [`udpsocket::peer_addr`]: https://doc.rust-lang.org/std/net/struct.UdpSocket.html#method.peer_addr
7814 ▶ [`todo!`]: https://doc.rust-lang.org/std/macro.todo.html
7815
7816
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)
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
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
65 the 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
227 Ok, now that we have constructed a `RegionInferenceContext`, we can do
41 We then apply them in while borrow-checking its parent in `TypeChecker::prove_closure_bounds`.
42
43 ▶ TODO: explain how exactly that works :3
44
1 # Reporting region errors
2
3 ▶ TODO: we should discuss how to generate errors from the results of these analyses.
4
8 the program.
9
10 ▶ TODO -- elaborate further? Maybe? :)
11
12 ## User types
123 trace!(?run, "entered Foo::should_run");
124
125 ▶ todo!()
126 }
127
· · ·
129 trace!(?run, "entered Foo::run");
130
131 ▶ todo!()
132 }
133 }
65 HIR Ty lowering can determine the type of the anon const by looking at the type of the Const Parameter that the anon const is an argument to.
66
67 ▶ TODO: write a chapter on query feeding and link it here
68
69 In some sense the desugarings from the previous examples are to:
115 which are effectively tests for a single variant.
116
117 ▶ ### Use "TODO" comments for things you don't want to forget
118
119 As a useful tool to yourself, you can insert a `// TODO` comment
· · ·
119 ▶ As a useful tool to yourself, you can insert a `// TODO` comment
120 for something that you want to get back to before you land your PR:
121
· · ·
123 fn 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
131 code 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
133 This can also be useful in a PR as a way to signal from one commit that you are
+ 1 more matches in this file
93 the trait object.
94
95 ▶ **TODO**: Figure out if the following should be mentioned in the GDB-Rust document rather than
96 this guide page so there is no duplication.
97 This is regarding the following comments:
· · ·
329 * New demangler in LLVM or LLDB.
330
331 ▶ **TODO**: Check the location of the demangler source.
332 [#1157](https://github.com/rust-lang/rustc-dev-guide/issues/1157)
333
181 # Source Information
182
183 ▶ TODO
453 Author: A U Thor <author@example.com>
454
455 ▶ -TODO: Describe a bug
456 +Describe a bug
457 @@ -324,5 +324,6
86 When building THIR we take the adjustments stored in the `TypeckResults` and make all of the coercion steps explicit. After this point in the compiler there isn't really a notion of coercions, only explicit casts and subtyping in the MIR.
87
88 ▶ TODO: write and link to an adjustments chapter here
89
90 ### How does `CoerceMany` work
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
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
607 [`ParseResult`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_expand/mbe/macro_parser/enum.ParseResult.html
608
609 ▶ <!-- TODO(rylev): more here. [#1160](https://github.com/rust-lang/rustc-dev-guide/issues/1160) -->
610
611 ### Custom Derive
· · ·
620 additional syntactic sugar and are allowed to be in namespaces.
621
622 ▶ <!-- TODO(rylev): more? [#1160](https://github.com/rust-lang/rustc-dev-guide/issues/1160) -->
623
56 rustc.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) -->
59 Filters 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
169 ### Cleanup paths
170
171 ▶ TODO: Discuss drop elaboration and unwinding.
172
173 ## Aside: drop elaboration and const-eval
195 the load is speculative.
196
197 ▶ ## TODO: [#16](https://github.com/rust-lang/rustc-dev-guide/issues/16)
198
199 This is a result of the first pass of learning the code.
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.
18 This makes sure there are no dangling [`Id`]s.
19
20 ▶ <!-- TODO: It does some more things too?
21 Also, talk about how it works
22 -->
86 ### The provisional cache
87
88 ▶ TODO: write this :3
89
90 - stack dependence of provisional results
431 }
432
433 ▶ fn bar<'b, T: Trait<'b>>() -> T::Assoc { todo!() }
434 fn foo<'a>()
435 where
· · ·
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 loginboth terms (AND is implicit) auth OR logineither term NOT path:vendorexclude matches "exact phrase"quoted exact match /func\s+Test/regex handler~1fuzzy (Levenshtein 1) file:*_test.gofilename glob path:pkg/auth/**full path glob lang:golanguage filter
Search any public repo from your terminal
This page calls POST /api/v1/code_search. Same tool, available over MCP for Claude/Cursor/Copilot.