-
Notifications
You must be signed in to change notification settings - Fork 133
/
2022-02-21-0.json
157 lines (157 loc) · 13 KB
/
2022-02-21-0.json
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
146
147
148
149
150
151
152
153
154
155
156
157
{
"description": "Do we want to make code in the error path tamper proof (and how tamper proof do we want it to be)?",
"refs": [
"https://github.com/nodejs/TSC/pull/1158"
],
"outcome": {
"winner(s)": [
"Use primordials in the error path only if there are no significant perf regression."
]
},
"votes": {
"aduh95": {
"Make the code in the error path full tamper proof by porting it away from JS/main thread (while we are waiting for a PR doing this, primordials should be used).": 1,
"Make the code in the error path full tamper proof by using primordials.": 2,
"Make the code in the error path full tamper proof by using primordials + a build step to use bind-this proposal syntax.": -1,
"Use primordials in the error path only if there are no significant perf regression.": 0,
"Don't use primordials for prototype methods (and undo existing ones) in the error path, keep using them otherwise.": 0,
"Don't use any primordials (and undo existing ones) in the error path.": -2
},
"BethGriggs": {
"Make the code in the error path full tamper proof by porting it away from JS/main thread (while we are waiting for a PR doing this, primordials should be used).": 1,
"Make the code in the error path full tamper proof by using primordials.": 1,
"Make the code in the error path full tamper proof by using primordials + a build step to use bind-this proposal syntax.": 1,
"Use primordials in the error path only if there are no significant perf regression.": 3,
"Don't use primordials for prototype methods (and undo existing ones) in the error path, keep using them otherwise.": 3,
"Don't use any primordials (and undo existing ones) in the error path.": 3
},
"BridgeAR": {
"Make the code in the error path full tamper proof by porting it away from JS/main thread (while we are waiting for a PR doing this, primordials should be used).": 0,
"Make the code in the error path full tamper proof by using primordials.": 0,
"Make the code in the error path full tamper proof by using primordials + a build step to use bind-this proposal syntax.": 0,
"Use primordials in the error path only if there are no significant perf regression.": 70,
"Don't use primordials for prototype methods (and undo existing ones) in the error path, keep using them otherwise.": 80,
"Don't use any primordials (and undo existing ones) in the error path.": 88
},
"cjihrig": {
"Make the code in the error path full tamper proof by porting it away from JS/main thread (while we are waiting for a PR doing this, primordials should be used).": 0,
"Make the code in the error path full tamper proof by using primordials.": 0,
"Make the code in the error path full tamper proof by using primordials + a build step to use bind-this proposal syntax.": 0,
"Use primordials in the error path only if there are no significant perf regression.": 0,
"Don't use primordials for prototype methods (and undo existing ones) in the error path, keep using them otherwise.": 0,
"Don't use any primordials (and undo existing ones) in the error path.": 0
},
"danielleadams": {
"Make the code in the error path full tamper proof by porting it away from JS/main thread (while we are waiting for a PR doing this, primordials should be used).": 0,
"Make the code in the error path full tamper proof by using primordials.": 0,
"Make the code in the error path full tamper proof by using primordials + a build step to use bind-this proposal syntax.": 0,
"Use primordials in the error path only if there are no significant perf regression.": 0,
"Don't use primordials for prototype methods (and undo existing ones) in the error path, keep using them otherwise.": 0,
"Don't use any primordials (and undo existing ones) in the error path.": 0
},
"gireeshpunathil": {
"Make the code in the error path full tamper proof by porting it away from JS/main thread (while we are waiting for a PR doing this, primordials should be used).": 5,
"Make the code in the error path full tamper proof by using primordials.": 3,
"Make the code in the error path full tamper proof by using primordials + a build step to use bind-this proposal syntax.": 4,
"Use primordials in the error path only if there are no significant perf regression.": 1,
"Don't use primordials for prototype methods (and undo existing ones) in the error path, keep using them otherwise.": 2,
"Don't use any primordials (and undo existing ones) in the error path.": 0
},
"jasnell": {
"Make the code in the error path full tamper proof by porting it away from JS/main thread (while we are waiting for a PR doing this, primordials should be used).": -1,
"Make the code in the error path full tamper proof by using primordials.": 0,
"Make the code in the error path full tamper proof by using primordials + a build step to use bind-this proposal syntax.": 0,
"Use primordials in the error path only if there are no significant perf regression.": 0,
"Don't use primordials for prototype methods (and undo existing ones) in the error path, keep using them otherwise.": -1,
"Don't use any primordials (and undo existing ones) in the error path.": -1
},
"joyeecheung": {
"Make the code in the error path full tamper proof by porting it away from JS/main thread (while we are waiting for a PR doing this, primordials should be used).": 3,
"Make the code in the error path full tamper proof by using primordials.": 1,
"Make the code in the error path full tamper proof by using primordials + a build step to use bind-this proposal syntax.": 0,
"Use primordials in the error path only if there are no significant perf regression.": 2,
"Don't use primordials for prototype methods (and undo existing ones) in the error path, keep using them otherwise.": 2,
"Don't use any primordials (and undo existing ones) in the error path.": 0
},
"mcollina": {
"Make the code in the error path full tamper proof by porting it away from JS/main thread (while we are waiting for a PR doing this, primordials should be used).": 0,
"Make the code in the error path full tamper proof by using primordials.": 2,
"Make the code in the error path full tamper proof by using primordials + a build step to use bind-this proposal syntax.": 1,
"Use primordials in the error path only if there are no significant perf regression.": 10,
"Don't use primordials for prototype methods (and undo existing ones) in the error path, keep using them otherwise.": 3,
"Don't use any primordials (and undo existing ones) in the error path.": 0
},
"mhdawson": {
"Make the code in the error path full tamper proof by porting it away from JS/main thread (while we are waiting for a PR doing this, primordials should be used).": 0,
"Make the code in the error path full tamper proof by using primordials.": 0,
"Make the code in the error path full tamper proof by using primordials + a build step to use bind-this proposal syntax.": 0,
"Use primordials in the error path only if there are no significant perf regression.": 5,
"Don't use primordials for prototype methods (and undo existing ones) in the error path, keep using them otherwise.": 0,
"Don't use any primordials (and undo existing ones) in the error path.": 4
},
"mmarchini": {
"Make the code in the error path full tamper proof by porting it away from JS/main thread (while we are waiting for a PR doing this, primordials should be used).": 0,
"Make the code in the error path full tamper proof by using primordials.": 0,
"Make the code in the error path full tamper proof by using primordials + a build step to use bind-this proposal syntax.": 0,
"Use primordials in the error path only if there are no significant perf regression.": 0,
"Don't use primordials for prototype methods (and undo existing ones) in the error path, keep using them otherwise.": 0,
"Don't use any primordials (and undo existing ones) in the error path.": 0
},
"MylesBorins": {
"Make the code in the error path full tamper proof by porting it away from JS/main thread (while we are waiting for a PR doing this, primordials should be used).": 0,
"Make the code in the error path full tamper proof by using primordials.": 0,
"Make the code in the error path full tamper proof by using primordials + a build step to use bind-this proposal syntax.": 0,
"Use primordials in the error path only if there are no significant perf regression.": 0,
"Don't use primordials for prototype methods (and undo existing ones) in the error path, keep using them otherwise.": 0,
"Don't use any primordials (and undo existing ones) in the error path.": 0
},
"RaisinTen": {
"Make the code in the error path full tamper proof by porting it away from JS/main thread (while we are waiting for a PR doing this, primordials should be used).": 0,
"Make the code in the error path full tamper proof by using primordials.": -1,
"Make the code in the error path full tamper proof by using primordials + a build step to use bind-this proposal syntax.": 0,
"Use primordials in the error path only if there are no significant perf regression.": -1,
"Don't use primordials for prototype methods (and undo existing ones) in the error path, keep using them otherwise.": 1,
"Don't use any primordials (and undo existing ones) in the error path.": 1
},
"richardlau": {
"Make the code in the error path full tamper proof by porting it away from JS/main thread (while we are waiting for a PR doing this, primordials should be used).": 2,
"Make the code in the error path full tamper proof by using primordials.": 0,
"Make the code in the error path full tamper proof by using primordials + a build step to use bind-this proposal syntax.": 0,
"Use primordials in the error path only if there are no significant perf regression.": 1,
"Don't use primordials for prototype methods (and undo existing ones) in the error path, keep using them otherwise.": 0,
"Don't use any primordials (and undo existing ones) in the error path.": 0
},
"ronag": {
"Make the code in the error path full tamper proof by porting it away from JS/main thread (while we are waiting for a PR doing this, primordials should be used).": 3,
"Make the code in the error path full tamper proof by using primordials.": 0,
"Make the code in the error path full tamper proof by using primordials + a build step to use bind-this proposal syntax.": 1,
"Use primordials in the error path only if there are no significant perf regression.": 2,
"Don't use primordials for prototype methods (and undo existing ones) in the error path, keep using them otherwise.": 4,
"Don't use any primordials (and undo existing ones) in the error path.": 5
},
"targos": {
"Make the code in the error path full tamper proof by porting it away from JS/main thread (while we are waiting for a PR doing this, primordials should be used).": 0,
"Make the code in the error path full tamper proof by using primordials.": 3,
"Make the code in the error path full tamper proof by using primordials + a build step to use bind-this proposal syntax.": 3,
"Use primordials in the error path only if there are no significant perf regression.": 2,
"Don't use primordials for prototype methods (and undo existing ones) in the error path, keep using them otherwise.": 1,
"Don't use any primordials (and undo existing ones) in the error path.": 0
},
"tniessen": {
"Make the code in the error path full tamper proof by porting it away from JS/main thread (while we are waiting for a PR doing this, primordials should be used).": -1,
"Make the code in the error path full tamper proof by using primordials.": 0,
"Make the code in the error path full tamper proof by using primordials + a build step to use bind-this proposal syntax.": -1,
"Use primordials in the error path only if there are no significant perf regression.": 0,
"Don't use primordials for prototype methods (and undo existing ones) in the error path, keep using them otherwise.": -1,
"Don't use any primordials (and undo existing ones) in the error path.": 0
},
"Trott": {
"Make the code in the error path full tamper proof by porting it away from JS/main thread (while we are waiting for a PR doing this, primordials should be used).": 0,
"Make the code in the error path full tamper proof by using primordials.": 0,
"Make the code in the error path full tamper proof by using primordials + a build step to use bind-this proposal syntax.": 0,
"Use primordials in the error path only if there are no significant perf regression.": 0,
"Don't use primordials for prototype methods (and undo existing ones) in the error path, keep using them otherwise.": 0,
"Don't use any primordials (and undo existing ones) in the error path.": 0
}
}
}