Compiler Team 2018-10-23 Retrospective
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

View only
 
ABCDEFGHIJKLMNOPQRSTUVWXYZAAABACADAEAF
1
😍 β€” Things that are awesome!😱 β€” Things that desperately need improvement
2
staying on tops of regressions basically works8rfcbot can idle for weeks1
3
positive friendly communication3xtriage meetings always over time, sometimes hung up on 1 thing2
4
work planning1hard to answer "what to do next" or "how can I help" 3xxxxxxxx
5
working groups as pathway to regular contribution4x
hard to find folks to fix regressions, particularly in some areas (e.g. LLVM)
2x
6
having clear goals (when we do)1hard to do high-level design + planning and not just triage4xxx
7
delegating and mentoring to newcomers7xxxno central place to get "big picture" of what's going on5xxx
8
public meetings on discord/zulip2xleaders stretched thin, need to scale up1x
9
error message work1xxxtechnical debt in compiler, heterogeneous structure2xxx
10
new crater (horray pietroalbini)1best practice workflow (--keep-stage etc) not well-documented or tested1xx
11
zulip1
perf regressions: we track, but don't always react unless someone complains
1
12
members are responsive on zulip/discord1xmore focus on features relevant to roadmap1x
13
implementation gets done3more focus on QoL improvements1x
14
consensus usually reached quickly2xMore regular reviewing of assigned PRs could be helpful1
15
code has debt, but not overwhelming1communication with IDE folks1xx
16
internals threads for public debate1Issues tagged T-compiler could use more info to get newbies started1
17
public roadmap1xxxxMore intermediate tasks for "newcomers"1x
18
blog posts on specific dev topics1xsometimes chaotic, held together by sheer force of will vs organization1
19
modules with low bus factor2xxx
20
more documentation, rustc book not easy enough to find2x
21
more standalone crates that can be independently built/tested1xx
22
faster build times (for building `rustc` itself)1xxxx
23
centralize on one chat platform 1x
24
bors time is long1xxxx
25
sometimes hard to know who to ask to review1x
26
Adding retrospectives in order to improve the iterations,1
27
having clear deadlines on issues when there is a rush1x
28
29
30
Priorities
31
fast compilation perf72%
32
RLS60%
33
cleanup, debt50%
34
trait system improvements40%
35
const generics36%
36
bors time36%
37
parallelized compilation31%
38
NLL improvements27%
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
Loading...