Version: 0.17.0
OS: CentOS 7

Hi Team,

I was trying to understand the effect of --reactive flag in infer run, infer capture and infer analyze, but got conflicting information from the Get Started guide and manual.

From man:

only in infer-analyze:
       --reactive,-r
           Activates: Reactive mode: the analysis starts from the files
           captured since the infer command started (Conversely:
           --no-reactive | -R)

infer-analyze:
       --changed-files-index file
           Specify the file containing the list of source files from which
           reactive analysis should start. Source files should be specified
           relative to project root or be absolute

However, in Recommended flow for CI,

1. infer capture --reactive -- make -j 4
   Apparently, one can also specify --reactive with infer capture, although man infer-capture doesn't have an entry for it.

What is its effect? Does it simply retain the infer-out folder and additively collect compiling artifacts?

2. infer analyze --reactive --changed-files-index index.txt
   "Reactive mode: the analysis starts from the files captured since the infer command started."
   I do understand it in the context of infer run, but in infer analyze, there are no "files captured since the infer command started".

What's a more accurate explanation of the effect of --reactive in infer-analyze?

3. infer analyze --changed-files-index index.txt
   "Specify the file containing the list of source files from which reactive analysis should start."

But it seems like --changed-files-index can be specified without --reactive.

Thanks!