Including libraries with conflicting parameter types should trigger a warning

[EvanMachusak]

Consider:

• CQL library A defines a parameter "P" whose type is Interval
• CQL Library B defines a parameter "P" whose type is Boolean
• A includes B

In many execution environments which only allow the user to supply a single value for each named parameter, trying to execute library A will be impossible, because parameter "P" cannot be simultaneously an Interval and a Boolean.

The translator should warn, and optionally by flag, cause an error when this is detected. This will help execution environments that assign parameter values globally protect themselves against parameter type conflicts.

[frankadrian314159]

Wouldn't the two P's be different? In library A, P (or A.P) would refer to A's P while one would have to explicitly reference B.P to see B's P. Since the two parameters have different access paths, there should be no collision. In reality, it is forcing these two different parameters to have a single value that causes the error and this is where the error should be fixed.