anchor.diff:  assert params.host.getHostName().equals("localhost");
   assert params.port == 12345;
   assert Arrays.equals(params.files, new File[] {new File("file1.txt"), new File("file2.txt")});
  -assert params.allParameters.equals(Arrays.asList("localhost", "12345", "file1.txt", "file2.txt"));
  +
  +assert params.allParameters.equals(Arrays.asList(args));
  +
   ----
   
   See <<Strongly Typed Everything>> for which types are supported out of the box and how to add custom types.
  +
  +==== Omitting the Index
  +It is possible to omit the `index` attribute. This means different things for single-value and for multi-value positional parameters.
  +
  +For *multi-value* positional parameters (arrays or collections), omitting the `index` attribute means the field captures _all_ positional parameters (the equivalent of `index = "0..*"`).
  +
  +For *single-value* positional parameters, picocli's behaviour has changed since version 4.3:
  +prior to picocli 4.3, the default index for single-value positional parameters was also `index = "0..*"`, even though only one value (usually the first argument) can be captured.
  +From version 4.3, picocli assigns an index automatically, based on the other positional parameters defined in the same command.
  +
  +[CAUTION]
  +====
  +Automatic indexes depend on the ability of Java reflection and Java annotation processors to iterate over fields in declaration order in the source code.
  +Officially this is not guaranteed by the Java spec.
  +In practice this has worked in Oracle JVMs and OpenJDK from Java 6, but there is some risk this may not work in the future or on other JVM's.
  +In general, for single-value positional parameters, using <<Explicit Index,explicit indexes>> is the safer option.
  +(Multi-value positional parameters can safely omit the `index` attribute.)
  +====
  +
  +IMPORTANT: Methods cannot be iterated over in predictable order.
  +For applications with <<option-parameters-methods,`@Parameters`-annotated methods>> or combinations of `@Parameters`-annotated methods and `@Parameters`-annotated fields, we recommend using <<Explicit Index,explicit indexes>> for single-value positional parameters.
  +
  +
  +See <<Automatic Parameter Indexes>> for details.
   
   === Mixing Options and Positional Parameters
   From picocli 2.0, positional parameters can be specified anywhere on the command line, they no longer need to follow the options.
  
positive.code:     }
  }
  ```
  
  === Boolean Options with Parameters
  By default the value of a boolean field is set to the logical negative of its default value when the option is specified on the command line.
  
negative.code: Any command line arguments that are not subcommands or options (or option parameters) are interpreted as positional parameters.
  Positional parameters generally follow the options but from picocli 2.0, positional parameters can be mixed with options on the command line.
  
  ==== Explicit Index
  
  Use the (zero-based) `index` attribute to specify exactly which parameters to capture.
  Array or collection fields can capture multiple values.
  
  The `index` attribute accepts _range_ values, so an annotation like `@Parameters(index="2..4")` captures the arguments at index 2, 3 and 4. Range values can be _open-ended_. For example, `@Parameters(index="3..*")` captures all arguments from index 3 and up.
  