File::Path::rmtree(): Interface 1: Use of Positional Parameters Is Suboptimal

• Uses positional parameters rather than named parameters.

• To alter the behavior, you have to remember: "Verbosity is the second position. Safety is the third position."

• What happens when maintainer wants to offer additional options for rmtree()?

• QUESTION: Is interface extensible?