If the programmer adds a specialization to a program that has previously been compiled, the pgprelnk program will notice that too and remove the assignment of the instantiation from the proper .ii file. The .ii files should not, in general, require any manual intervention. The name in the message is the mangled name of the entity. The automatic instantiation scheme can coexist with partial explicit control of instantiation by the programmer through the use of pragmas or command-line specification of the instantiation mode. C exists, and if so it will process it as if it were included at the end of the main source file.
Implicit inclusion works well alongside automatic instantiation, but the two are independent.
They can be enabled or disabled independently, and implicit inclusion is still useful when automatic instantiation is not done. A common means of investigating certain kinds of problems is to produce a preprocessed source file that can be inspected. When using implicit inclusion it is sometimes desirable for the preprocessed source file to include any implicitly included files. This causes the preprocessed output to be generated as part of a normal compilation. When implicit inclusion is being used, the implicitly included files will appear as part of the preprocessed output in the precise location at which they were included in the compilation.