diff options
author | jimingham <jingham@apple.com> | 2024-06-07 17:05:29 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-06-07 17:05:29 -0700 |
commit | 435dd9746107e13c2ad019be3bd34815f7d2360d (patch) | |
tree | 7b41ef6aaeea109ff5a670934e4d8d74f4803e03 /llvm/unittests/ProfileData/MemProfTest.cpp | |
parent | c8eff8788f1052398176f3aca5aebbd12368920a (diff) | |
download | llvm-435dd9746107e13c2ad019be3bd34815f7d2360d.zip llvm-435dd9746107e13c2ad019be3bd34815f7d2360d.tar.gz llvm-435dd9746107e13c2ad019be3bd34815f7d2360d.tar.bz2 |
Add AllowRepeats to SBCommandInterpreterRunOptions. (#94786)
This is useful if you have a transcript of a user session and want to
rerun those commands with RunCommandInterpreter. The same functionality
is also useful in testing.
I'm adding it primarily for the second reason. In a subsequent patch,
I'm adding the ability to Python based commands to provide their
"auto-repeat" command. Among other things, that will allow potentially
state destroying user commands to prevent auto-repeat. Testing this with
Shell or pexpect tests is not nearly as accurate or convenient as using
RunCommandInterpreter, but to use that I need to allow auto-repeat.
I think for consistency's sake, having interactive sessions always do
auto-repeats is the right choice, though that's a lightly held
opinion...
Diffstat (limited to 'llvm/unittests/ProfileData/MemProfTest.cpp')
0 files changed, 0 insertions, 0 deletions