diff options
| author | walter erquinigo <walter@modular.com> | 2023-08-11 18:27:37 -0400 |
|---|---|---|
| committer | walter erquinigo <walter@modular.com> | 2023-08-22 12:27:08 -0400 |
| commit | a4dbdf4749938396dbf913478289fa426d8341ae (patch) | |
| tree | 92a89308dcad10020a0c3413c32fc47a9a460349 /clang/lib/ExtractAPI/DeclarationFragments.cpp | |
| parent | a1c736ec08f25e83552b20c94a5b2afdcd021a40 (diff) | |
| download | llvm-a4dbdf4749938396dbf913478289fa426d8341ae.zip llvm-a4dbdf4749938396dbf913478289fa426d8341ae.tar.gz llvm-a4dbdf4749938396dbf913478289fa426d8341ae.tar.bz2 | |
[LLDB] Allow expression evaluators to set arbitrary timeouts
https://github.com/llvm/llvm-project/commit/59237bb52c9483fce395428bfab5996eabe54ed0 changed the behavior of the `SetTimeout` and `GetTimeout` methods of `EvaluateExpressionOptions`, which broke the Mojo REPL and related services (https://docs.modular.com/mojo/) because it relies on having infinite timeouts. That's a necessity because developers often use the REPL for executing extremely long-running numeric jobs. Having said that, `EvaluateExpressionOptions` shouldn't be that opinionated on this matter anyway. Instead, it should be the responsibility of the evaluator to define which timeout to use for each specific case.
Differential Revision: https://reviews.llvm.org/D157764
Diffstat (limited to 'clang/lib/ExtractAPI/DeclarationFragments.cpp')
0 files changed, 0 insertions, 0 deletions