SA1135 inconsistent regarding use of aliases

[bjornhellander]

Consider the following code:

using Tasks = System.Threading.Tasks;

namespace TestStuff
{
    using T1 = Tasks.Task; // No warning here
    using T2 = System.ValueTuple<Tasks.Task, int>; // Warning here
}

SA1135 seems to allow the use of aliases in using directives. Since there is no warning for the use of Tasks.Task when defining T1, I would not expect a warning when defining T2 either.

Tested using version 1.2.0-beta.556

[sharwell]

What happens if you use Tasks::Task instead?

[bjornhellander]

No warnings when using Tasks::Task instead in the original example.

Not in this example either, which also seems weird:

using System;
using Tasks = System.Threading.Tasks;

namespace TestStuff
{
    using T2 = ValueTuple<Tasks::Task, int>; // No warning here because of ValueType not being fully qualified
}