rust/src/test/debuginfo/generator-objects.rs, branch try

Move /src/test to /tests

2023-01-11T09:32:08+00:00

Use enum2<_> instead of enum<_> for Cpp-like debuginfo enum type names.

2022-08-12T08:53:07+00:00

And add more comments about niche tag enum encoding.

debuginfo: Change C++-like encoding for enums.

2022-08-12T08:53:07+00:00

The updated encoding should be able to handle niche layouts where more than one variant has fields.

debuginfo: Refactor debuginfo generation for types -- Make generator-objects test case architecture independent.

2022-03-15T10:45:51+00:00

debuginfo: change cpp-like naming for generator environments so that NatVis works for them

2022-03-14T15:52:47+00:00

debuginfo: Make sure that type names for closure and generator environments are unique in debuginfo.

2022-02-01T09:39:40+00:00

Before this change, closure/generator environments coming from different instantiations of the same generic function were all assigned the same name even though they were distinct types with potentially different data layout. Now we append the generic arguments of the originating function to the type name. This commit also emits '{closure_env#0}' as the name of these types in order to disambiguate them from the accompanying closure function '{closure#0}'. Previously both were assigned the same name.

Store names of captured variables in `optimized_mir`

2021-07-09T15:09:48+00:00

- Closures in external crates may get compiled in because of monomorphization. We should store names of captured variables in `optimized_mir`, so that they are written into the metadata file and we can use them to generate debuginfo. - If there are breakpoints inside closures, the names of captured variables stored in `optimized_mir` can be used to print them. Now the name is more precise when disjoint fields are captured.

Name the captured upvars for closures/generators in debuginfo

2021-07-09T15:06:53+00:00

Previously, debuggers print closures as something like ``` y::main::closure-0 (0x7fffffffdd34) ``` The pointer actually references to an upvar. It is not very obvious, especially for beginners. It's because upvars don't have names before, as they are packed into a tuple. This commit names the upvars, so we can expect to see something like ``` y::main::closure-0 {_captured_ref__b: 0x[...]} ```

Improve debug symbol names to avoid ambiguity and work better with MSVC's debugger

2021-06-30T18:10:29+00:00

There are several cases where names of types and functions in the debug info are either ambiguous, or not helpful, such as including ambiguous placeholders (e.g., `{{impl}}`, `{{closure}}` or `dyn _'`) or dropping qualifications (e.g., for dynamic types). Instead, each debug symbol name should be unique and useful: * Include disambiguators for anonymous `DefPathDataName` (closures and generators), and unify their formatting when used as a path-qualifier vs item being qualified. * Qualify the principal trait for dynamic types. * If there is no principal trait for a dynamic type, emit all other traits instead. * Respect the `qualified` argument when emitting ref and pointer types. * For implementations, emit the disambiguator. * Print const generics when emitting generic parameters or arguments. Additionally, when targeting MSVC, its debugger treats many command arguments as C++ expressions, even when the argument is defined to be a symbol name. As such names in the debug info need to be more C++-like to be parsed correctly: * Avoid characters with special meaning (`#`, `[`, `"`, `+`). * Never start a name with `<` or `{` as this is treated as an operator. * `>>` is always treated as a right-shift, even when parsing generic arguments (so add a space to avoid this). * Emit function declarations using C/C++ style syntax (e.g., leading return type). * Emit arrays as a synthetic `array$` type. * Include a `$` in all synthetic types as this is a legal character for C++, but not Rust (thus we avoid collisions with user types).

Remove artificial flag from generator variants

2021-04-30T14:36:08+00:00

- Literally, variants are not artificial. We have `yield` statements, upvars and inner variables in the source code. - Functionally, we don't want debuggers to suppress the variants. It contains the state of the generator, which is useful when debugging. So they shouldn't be marked artificial. - Debuggers may use artificial flags to find the active variant. In this case, marking variants artificial will make debuggers not work properly. Fixes #79009.