1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
|
//// [tests/cases/compiler/readonlyPropertySubtypeRelationDirected.ts] ////
//// [one.ts]
export {};
// When the non-readonly type is declared first, the unioned type of `three` in `doSomething` is never treated as readonly
const two: { a: string } = { a: 'two' };
const one: { readonly a: string } = { a: 'one' };
function doSomething(condition: boolean) {
// when `one` comes first in the conditional check, the return type of `doSomething` is inferred as `a` is readonly, but `a` is
// only treated as readonly (i.e. it will produce a diagnostic if you try to assign to it) based on the order of declarations of `one` and `two` above
const three = (condition) ? one : two;
three.a = 'foo';
// the inferred (displayed?) type of `a` also depends on the order of the condition above. When `one` comes first, the displayed type is `any`
// when `two` comes first, the displayed type is `string`, but the diagnostic will always correctly find that it's string
three.a = 'foo2';
return three;
}
//// [two.ts]
export {};
// When the non-readonly type is declared first, the unioned type of `three` in `doSomething` is never treated as readonly
const two: { a: string } = { a: 'two' };
const one: { readonly a: string } = { a: 'one' };
function doSomething(condition: boolean) {
// when `two` comes first in the conditional check, the return type of `doSomething` is inferred as not readonly but produces the same diagnostics as above
// based on the declaration order of `one` and `two`
const three = (condition) ? two : one;
three.a = 'foo';
// the inferred (displayed?) type of `a` also depends on the order of the condition above. When `one` comes first, the displayed type is `any`
// when `two` comes first, the displayed type is `string`, but the diagnostic will always correctly find that it's string
three.a = 'foo2';
return three;
}
//// [three.ts]
export {};
// When the readonly type is declared first, the unioned type of `three` in `doSomething` is always treated as readonly by the compiler
const one: { readonly a: string } = { a: 'one' };
const two: { a: string } = { a: 'two' };
function doSomething(condition: boolean) {
// when `one` comes first in the conditional check, the return type of `doSomething` is inferred as `a` is readonly, but `a` is
// only treated as readonly (i.e. it will produce a diagnostic if you try to assign to it) based on the order of declarations of `one` and `two` above
const three = (condition) ? one : two;
three.a = 'foo';
// the inferred (displayed?) type of `a` also depends on the order of the condition above. When `one` comes first, the displayed type is `any`
// when `two` comes first, the displayed type is `string`, but the diagnostic will always correctly find that it's string
three.a = 'foo2';
return three;
}
//// [four.ts]
export {};
// When the readonly type is declared first, the unioned type of `three` in `doSomething` is always treated as readonly by the compiler
const one: { readonly a: string } = { a: 'one' };
const two: { a: string } = { a: 'two' };
function doSomething(condition: boolean) {
// when `two` comes first in the conditional check, the return type of `doSomething` is inferred as not readonly but produces the same diagnostics as above
// based on the declaration order of `one` and `two`
const three = (condition) ? two : one;
three.a = 'foo';
// the inferred (displayed?) type of `a` also depends on the order of the condition above. When `one` comes first, the displayed type is `any`
// when `two` comes first, the displayed type is `string`, but the diagnostic will always correctly find that it's string
three.a = 'foo2';
return three;
}
//// [one.js]
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
// When the non-readonly type is declared first, the unioned type of `three` in `doSomething` is never treated as readonly
var two = { a: 'two' };
var one = { a: 'one' };
function doSomething(condition) {
// when `one` comes first in the conditional check, the return type of `doSomething` is inferred as `a` is readonly, but `a` is
// only treated as readonly (i.e. it will produce a diagnostic if you try to assign to it) based on the order of declarations of `one` and `two` above
var three = (condition) ? one : two;
three.a = 'foo';
// the inferred (displayed?) type of `a` also depends on the order of the condition above. When `one` comes first, the displayed type is `any`
// when `two` comes first, the displayed type is `string`, but the diagnostic will always correctly find that it's string
three.a = 'foo2';
return three;
}
//// [two.js]
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
// When the non-readonly type is declared first, the unioned type of `three` in `doSomething` is never treated as readonly
var two = { a: 'two' };
var one = { a: 'one' };
function doSomething(condition) {
// when `two` comes first in the conditional check, the return type of `doSomething` is inferred as not readonly but produces the same diagnostics as above
// based on the declaration order of `one` and `two`
var three = (condition) ? two : one;
three.a = 'foo';
// the inferred (displayed?) type of `a` also depends on the order of the condition above. When `one` comes first, the displayed type is `any`
// when `two` comes first, the displayed type is `string`, but the diagnostic will always correctly find that it's string
three.a = 'foo2';
return three;
}
//// [three.js]
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
// When the readonly type is declared first, the unioned type of `three` in `doSomething` is always treated as readonly by the compiler
var one = { a: 'one' };
var two = { a: 'two' };
function doSomething(condition) {
// when `one` comes first in the conditional check, the return type of `doSomething` is inferred as `a` is readonly, but `a` is
// only treated as readonly (i.e. it will produce a diagnostic if you try to assign to it) based on the order of declarations of `one` and `two` above
var three = (condition) ? one : two;
three.a = 'foo';
// the inferred (displayed?) type of `a` also depends on the order of the condition above. When `one` comes first, the displayed type is `any`
// when `two` comes first, the displayed type is `string`, but the diagnostic will always correctly find that it's string
three.a = 'foo2';
return three;
}
//// [four.js]
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
// When the readonly type is declared first, the unioned type of `three` in `doSomething` is always treated as readonly by the compiler
var one = { a: 'one' };
var two = { a: 'two' };
function doSomething(condition) {
// when `two` comes first in the conditional check, the return type of `doSomething` is inferred as not readonly but produces the same diagnostics as above
// based on the declaration order of `one` and `two`
var three = (condition) ? two : one;
three.a = 'foo';
// the inferred (displayed?) type of `a` also depends on the order of the condition above. When `one` comes first, the displayed type is `any`
// when `two` comes first, the displayed type is `string`, but the diagnostic will always correctly find that it's string
three.a = 'foo2';
return three;
}
|
