[LifetimeSafety] Reorganize diagnostic groups and remove confidence-based warnings (#179309)
Reorganized lifetime safety diagnostic groups to be more granular and
renamed diagnostic messages for better clarity.
- **Diagnostic Group Restructuring**: Split lifetime safety warnings
into more specific categories:
- `lifetime-safety-use-after-scope` and
`lifetime-safety-use-after-scope-moved` for scope-related issues
- `lifetime-safety-return-stack-addr` and
`lifetime-safety-return-stack-addr-moved` for return address issues
- `lifetime-safety-dangling-field` and
`lifetime-safety-dangling-field-moved` for field reference issues
- Added new umbrella groups `lifetime-safety-validations` and
`lifetime-safety-all`
- **Diagnostic Message Updates**: Renamed warning diagnostics from
generic "loan expires" terminology to more specific messages like "use
after scope" and "return stack addr"
- **Code Cleanup**: Removed `Confidence` logic (based on possible vs
guaranteed control-flow) from diagnostic reporting functions. Added TODO
comment to deprecate the `Confidence` enum
The new diagnostic group tree is:
```
lifetime-safety-all
├── lifetime-safety
│ ├── lifetime-safety-permissive
│ │ ├── lifetime-safety-use-after-scope
│ │ ├── lifetime-safety-return-stack-addr
│ │ └── lifetime-safety-dangling-field
│ └── lifetime-safety-strict
│ ├── lifetime-safety-use-after-scope-moved
│ ├── lifetime-safety-return-stack-addr-moved
│ ├── lifetime-safety-dangling-field-moved
│ └── lifetime-safety-invalidation
├── lifetime-safety-suggestions
│ ├── lifetime-safety-cross-tu-suggestions
│ └── lifetime-safety-intra-tu-suggestions
└── lifetime-safety-validations
└── lifetime-safety-noescape
```
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.