llvm-project.git/lldb/source/Plugins/Language/CPlusPlus/LibCxxProxyArray.cpp, branch users/nico/python-2

[lldb][DataFormatters] Change ExtractIndexFromString to return std::optional (#138297)

2025-05-08T11:21:26+00:00

This PR is in continuation of
https://github.com/llvm/llvm-project/pull/136693.

[lldb] Upgrade `GetIndexOfChildWithName` to use `llvm::Expected` (#136693)

2025-04-30T10:44:19+00:00

This patch replaces the use of `UINT32_MAX` as the error return value of
`GetIndexOfChildWithName` with `llvm::Expected`.


# Tasks to do in another PR

1. Replace `CalculateNumChildrenIgnoringErrors` with
`CalculateNumChildren`. See [this
comment](https://github.com/llvm/llvm-project/pull/136693#discussion_r2056319358).
2. Update `lldb_private::formatters::ExtractIndexFromString` to use
`llvm::Expected`. See [this
comment](https://github.com/llvm/llvm-project/pull/136693#discussion_r2054217536).
3. Create a new class which carries both user and internal errors. See
[this
comment](https://github.com/llvm/llvm-project/pull/136693#discussion_r2056439608).

[lldb] Upgrade CompilerType::GetBitSize to return llvm::Expected (#129601)

2025-03-05T18:21:19+00:00

This patch pushes the error handling boundary for the GetBitSize()
methods from Runtime into the Type and CompilerType APIs. This makes it
easier to diagnose problems thanks to more meaningful error messages
being available. GetBitSize() is often the first thing LLDB asks about a
type, so this method is particularly important for a better user
experience.

rdar://145667239

[lldb] Provide default impl for MightHaveChildren (NFC) (#119977)

2025-02-17T19:19:14+00:00

The vast majority of `SyntheticChildrenFrontEnd` subclasses provide
children, and as such implement `MightHaveChildren` with a constant
value of `true`. This change makes `true` the default value. With this
change, `MightHaveChildren` only needs to be implemented by synthetic
providers that can return `false`, which is only 3 subclasses.

[lldb] Move ValueObject into its own library (NFC) (#113393)

2024-10-25T03:20:48+00:00

ValueObject is part of lldbCore for historical reasons, but conceptually
it deserves to be its own library. This does introduce a (link-time) circular
dependency between lldbCore and lldbValueObject, which is unfortunate
but probably unavoidable because so many things in LLDB rely on
ValueObject. We already have cycles and these libraries are never built
as dylibs so while this doesn't improve the situation, it also doesn't
make things worse.

The header includes were updated with the following command:

```
find . -type f -exec sed -i.bak "s%include \"lldb/Core/ValueObject%include \"lldb/ValueObject/ValueObject%" '{}' \;
```

[LLDB][libc++] Adds valarray proxy data formatters. (#88613)

2024-04-15T16:46:58+00:00

These proxies are returned by operator[](...). These proxies all
"behave" the same. They store a pointer to the data of the valarray they
are a proxy for and they have an internal array of indices. This
internal array is considered its contents.