diff options
| author | walter erquinigo <walter@modular.com> | 2023-08-11 18:27:37 -0400 |
|---|---|---|
| committer | walter erquinigo <walter@modular.com> | 2023-08-22 17:41:14 -0400 |
| commit | 7822e5dbf1cb4be2d73eb13da27b04de684c318b (patch) | |
| tree | 8306a30a1942cd0ccc17d0f582ef8cd767ee98ea /clang/lib/ExtractAPI/DeclarationFragments.cpp | |
| parent | 9b6b6bbc9127d604881cdc9dcea0e7c74ef821fd (diff) | |
| download | llvm-7822e5dbf1cb4be2d73eb13da27b04de684c318b.zip llvm-7822e5dbf1cb4be2d73eb13da27b04de684c318b.tar.gz llvm-7822e5dbf1cb4be2d73eb13da27b04de684c318b.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