|
| 1 | +# November 20th, 2017 |
| 2 | + |
| 3 | +Agenda week, Vidyo meeting: 2018 planning |
| 4 | + |
| 5 | +## Notes |
| 6 | + |
| 7 | +The meeting covered initial planning for dev tools in 2018. This was basically |
| 8 | +'requirements gathering' and brain storming, with no attempt at prioritisation |
| 9 | +yet. |
| 10 | + |
| 11 | + |
| 12 | +### Some overall thoughts |
| 13 | + |
| 14 | +* Lots of ongoing work from this year |
| 15 | +* Likely that consolidation will be a big part of next year's work |
| 16 | +* Debugging is a big area for work. |
| 17 | +* Moving Rustup functionality into Cargo will be very user-facing |
| 18 | +* Continue to improve workflow around tools distribution (and integration with Rust repo). |
| 19 | +* We should improve tool ergonomics across the board |
| 20 | + - in particular being on nightly sucks |
| 21 | +* Could we abstract over the compiler a bit more to have a uniform API for tools? |
| 22 | + |
| 23 | + |
| 24 | +### WASM |
| 25 | + |
| 26 | +* Possibly big next year |
| 27 | +* What will debugging look like |
| 28 | + - Can we ensure Rust will be well-supported (c.f., DWARF) |
| 29 | +* Build tools, webpack integration (already started) |
| 30 | + |
| 31 | + |
| 32 | +### IDEs |
| 33 | + |
| 34 | +* Refactoring |
| 35 | +* Debugging |
| 36 | + |
| 37 | +RLS: |
| 38 | + |
| 39 | +* 1.0 |
| 40 | +* compiler-driven code completion |
| 41 | +* stability (users and clients need it) |
| 42 | +* better Clippy integration (Rustfix approach? - killercup) |
| 43 | + |
| 44 | +IntelliJ: |
| 45 | + |
| 46 | +* macro support |
| 47 | +* feature work - refactoring, etc. |
| 48 | +* debugging - blocked on CLion (need to make it work with Cargo) |
| 49 | + |
| 50 | + |
| 51 | +### Debugging |
| 52 | + |
| 53 | +Goal: less pain! |
| 54 | + |
| 55 | +* LLDB support |
| 56 | +* better Dwarf info from compiler in parallel with debuggers |
| 57 | +* expression parsing - can we recycle bits of the compiler? Lots of trade-offs! |
| 58 | + |
| 59 | + |
| 60 | +### Rustdoc |
| 61 | + |
| 62 | +New rustdoc: |
| 63 | + |
| 64 | +* exist! |
| 65 | +* on a par with current rustdoc |
| 66 | + - good enough to stop working on current rustdoc, not necessarily bug-for-bug compatible |
| 67 | +* experiment with stuff (book views, source exploration, etc) |
| 68 | + |
| 69 | +Current rustdoc: |
| 70 | + |
| 71 | +* Continue incremental improvements |
| 72 | +* paths/links RFC (compiler work) |
| 73 | + |
| 74 | + |
| 75 | +### Clippy |
| 76 | + |
| 77 | +* rustup distribution |
| 78 | +* more lints |
| 79 | +* factor util code into rustc? (Abstraction layer?) |
| 80 | +* 1.0 release |
| 81 | +* improve suggestions (auto-application, rustfix) |
| 82 | + |
| 83 | + |
| 84 | +### Testing |
| 85 | + |
| 86 | +* extensibility is important |
| 87 | +* also nice to have better default system - setup/teardown, etc. |
| 88 | +* can we make it extensible enough to experiment with? |
| 89 | +* inspecting output in IDEs |
| 90 | +* JSON output |
| 91 | +* fuzzing |
| 92 | +* doc tests too want setup/teardown |
| 93 | + |
| 94 | + |
| 95 | +### Cargo and Xargo |
| 96 | + |
| 97 | +* support local registries |
| 98 | + |
| 99 | +Xargo: |
| 100 | + |
| 101 | +* make it part of Cargo and disappear! |
| 102 | +* coordinate with rustup into Cargo stuff |
| 103 | + |
0 commit comments