Report errors on properties and variable type visibility
Fixes #69
Test baselines because of change
Emit unexported aliases that need to be emitted to .d.ts to make correct result
Test baselines after asynchronous alias declaration writing
Ambient module declarations (exception import declaration) are visible
Test case for the privacy check of variables and properties during declaration emit
Report privacy errors on parameter types
Report privacy errors on return types
Report privacy errors for accessors
Emit the declarations for the chained import usage in the export assignment
Removing bug numbers from the testcases which are fixed and adding declaration generation in few testcases
Fix the incorrect declaration file path during d.ts file compile in the compilerrunner
Enable project runner to compile generated .d.ts files
Uncovered bug in quoted .d.ts compilation
Update the project runner to emit errors in more readable way
Check for the accessible symbol from exported import

eg:
// @Filename: w1.ts
export = Widget1
class Widget1 { name = 'one'; }

// @Filename: exporter.ts
export import w = require('./w1');

// @Filename: consumer.ts
import e = require('./exporter');

export function w(): e.w { // Should be OK
    return new e.w();
}

In this looking for the name of return type of function w,
not just look for the alias == SymbolOfReturnType but also
look for alias.exportedSymbols === symbolOfReturnType
and qualify it during the toString
Report error if the entityname reference in the import declaration is using private module
Use typeof function in the declaration emitter instead of unwinding first level
During qualification if we are looking in value space, the left qualifier meaning is also value
Make changes to report error if the type used from external module cannot be named
Adds test cases too
Merge pull request #431 from Microsoft/cannotName

Make changes to report error if the type used from external module cannot be named