tsconfig: using out option results in really ugly/duplicated output.

[niemyjski]

I'm using a tsconfig file in our project: https://github.com/exceptionless/Exceptionless.Javascript and I'm seeing the following behavior (Everything is in the same module, but multiple files..).

I feel that all code should be placed into the same module region when it's generated.

[DanielRosenwasser]

That would be incorrect because we need to respect initialization order.

module m {
    export var x = 10;
}

var y = 20;

function f(x: number) {
    return 2 * x;
}

module m { 
    export var z = f(x + y);
}

It would be inappropriate to place the initialization of z at the same location as x given that its value relies on y, which was initialized before it.

[niemyjski]

I'm not saying you shouldn't respect the initializing order, I'm just saying it feels insane that I need to have duplicated

in my single module (one of those per file)... It could just place one around everything in that module file.. Please reopen this.. As you've just increased by javascript file size by N.

[mhegazy]

@niemyjski it is true that `var Exceptionless;

[niemyjski]

I'm talking about var Exceptionless and extra function wrappers

[niemyjski]

I wonder what the extra var Exceptionless; will do in existing/order browsers

[mhegazy]

fixing my comment. @niemyjski it is true that var Exceptionless; can be dropped. and it would make the code look cleaner. I am not sure i see the implementation cost vs the aesthetic return value .

[niemyjski]

It doesn't look like code I would write... And that is what typescripts supposed to do..

[mhegazy]

We have maintained an axiom not to change user code when possible. the problem with merging these scopes, is we will have to rename declarations if they conflict.

[niemyjski]

But you are using my tsconfig. That has of all my dependencies so you should have all the info in the parse result to make the right decision.