Definition at line 230 of file NSSet.cpp.
◆ NSSetCodeRunningSyntheticFrontEnd()
lldb_private::formatters::NSSetCodeRunningSyntheticFrontEnd::NSSetCodeRunningSyntheticFrontEnd |
( |
lldb::ValueObjectSP |
valobj_sp | ) |
|
◆ ~NSSetCodeRunningSyntheticFrontEnd()
lldb_private::formatters::NSSetCodeRunningSyntheticFrontEnd::~NSSetCodeRunningSyntheticFrontEnd |
( |
| ) |
|
|
override |
◆ CalculateNumChildren()
llvm::Expected< uint32_t > lldb_private::formatters::NSSetCodeRunningSyntheticFrontEnd::CalculateNumChildren |
( |
| ) |
|
|
overridevirtual |
◆ GetChildAtIndex()
lldb::ValueObjectSP lldb_private::formatters::NSSetCodeRunningSyntheticFrontEnd::GetChildAtIndex |
( |
uint32_t |
idx | ) |
|
|
overridevirtual |
◆ GetIndexOfChildWithName()
size_t lldb_private::formatters::NSSetCodeRunningSyntheticFrontEnd::GetIndexOfChildWithName |
( |
ConstString |
name | ) |
|
|
overridevirtual |
◆ MightHaveChildren()
bool lldb_private::formatters::NSSetCodeRunningSyntheticFrontEnd::MightHaveChildren |
( |
| ) |
|
|
overridevirtual |
◆ Update()
This function is assumed to always succeed and if it fails, the front-end should know to deal with it in the correct way (most probably, by refusing to return any children).
The return value of Update should actually be interpreted as "ValueObjectSyntheticFilter cache is good/bad". If this function returns lldb::ChildCacheState::eReuse, ValueObjectSyntheticFilter is allowed to use the children it fetched previously and cached. Otherwise, ValueObjectSyntheticFilter must throw away its cache, and query again for children.
Implements lldb_private::SyntheticChildrenFrontEnd.
The documentation for this class was generated from the following file: