Go, pls stop breaking my editor – Rebecca Stambler

Transcript

1. Go, pls stop breaking my editor MOSCOW, RUSSIA APRIL 13 2019 REBECCA STAMBLER
5. Go,
6. Go, please stop breaking my editor!
7. Rebecca Stambler Software Engineer, Google @stamblerre
13. My editor isn’t working!
14. My editor isn’t working! • There are many different editors and many different features
15. VSCode Goland Vim
16. My editor isn’t working! • There are many different editors and many different features • Many features are slow
17. My editor isn’t working! • There are many different editors and many different features • Many features are slow • New Go releases break features
19. My editor isn’t working! • There are many different editors and many different features
20. User triggers go-to-definition
21. User triggers go-to-definition VSCode Go extension
22. User triggers go-to-definition VSCode Go extension godef
23. User triggers go-to-definition VSCode Go extension godef
24. User triggers go-to-definition VSCode Go extension godef VSCode opens file at the specified position
25. godef gopkgs go-outline go-symbols VSCode guru gorename gomodifytags goplay Go extension
26. godef gopkgs go-outline go-symbols VSCode guru gorename gomodifytags goplay impl gotype-live gocode gogetdoc goimports goreturns goformat golint Go extension
27. godef gopkgs go-outline go-symbols VSCode guru gorename gomodifytags goplay impl gotype-live gocode gogetdoc goimports goreturns goformat golint gotests gometalinter staticcheck golangci-lint revive fillstruct dlv godoctor Go extension
28. godef gopkgs go-outline go-symbols guru gorename gomodifytags goplay impl gotype-live gocode gogetdoc goimports goreturns goformat golint gotests gometalinter staticcheck golangci-lint revive fillstruct dlv godoctor
29. My editor isn’t working! • There are many different editors and many different features • Many features are slow
30. Command-line tools
31. Command-line tools • Most of these tools work on 1 request per process
32. Command-line tools • Most of these tools work on 1 request per process • The tool has to parse your file and type-check your dependencies EVERY TIME!
33. My editor isn’t working! • There are many different editors and many different features • Many features are slow • New Go releases break features
34. An example
35. An example: gocode • A tool for autocompletion
36. An example: gocode • A tool for autocompletion • Go 1.10 broke nsf/gocode
37. An example: gocode • A tool for autocompletion • Go 1.10 broke nsf/gocode • Fixed in mdempsky/gocode
38. An example: gocode • A tool for autocompletion • Go 1.10 broke nsf/gocode • Fixed in mdempsky/gocode • And then...Go modules
39. An example: gocode • A tool for autocompletion • Go 1.10 broke nsf/gocode • Fixed in mdempsky/gocode • And then...Go modules • Resulting in stamblerre/gocode
40. Takeaways • At this rate, we will have a version of gocode for every version of Go
41. Takeaways • At this rate, we will have a version of gocode for every version of Go • Your tools shouldn’t break when you upgrade
42. Why did gocode keep breaking?
43. Why did gocode keep breaking? • When Go changes, tools change
44. Why did gocode keep breaking? • When Go changes, tools change • When go build changes, tools change more
45. Why did gocode keep breaking? • When Go changes, tools change • When go build changes, tools change more • Tools copy the behavior of the Go compiler
46. foo.go
47. foo.go github.com/stamblerre/foo
48. foo.go github.com/stamblerre/foo a c b dependencies
50. How will we fix your editor?
51. How will we fix your editor? 1. Stop tools from breaking every 6 months
52. How will we fix your editor? 1. Stop tools from breaking every 6 months 2. Support a set of features for all editors
53. How will we fix your editor? 1. Stop tools from breaking every 6 months
54. gocode
55. go/packages gocode
56. go/packages gocode Which build system am I running in?
57. go/packages gocode Which build system am I running in? go 1.10 go 1.11 gb go 1.12
58. go/packages • Reduces the maintenance burden
59. go/packages • Reduces the maintenance burden • When a new Go release comes out, fix the driver, not the tools
60. How will we fix your editor? 1. Stop tools from breaking every 6 months 2. Support a set of features for all editors
61. Language Server Protocol A standardized protocol for communication between editors and language servers
62. godef gopkgs go-outline go-symbols guru gorename gomodifytags goplay impl gotype-live gocode gogetdoc goimports goreturns goformat golint gotests gometalinter staticcheck golangci-lint revive fillstruct dlv godoctor
63. Go language server
64. gopls
65. gopls • The Go language server
66. gopls • The Go language server • Owned and maintained by the Go team and community
67. gopls • The Go language server • Owned and maintained by the Go team and community • Currently in alpha
68. gopls • The Go language server • Owned and maintained by the Go team and community • Currently in alpha • Pronounced “Go please”
69. gopls is faster • All features benefit from caching
70. gopls is faster • All features benefit from caching • Completion is noticeably faster (less than 1 ms)
71. gopls is faster • All features benefit from caching • Completion is noticeably faster (less than 1 ms) • Remains fast with modules
72. gopls is extensible • Adding new features is easier
73. gopls is extensible • Adding new features is easier • Planned:
74. gopls is extensible • Adding new features is easier • Planned: ◦ References, rename
75. gopls is extensible • Adding new features is easier • Planned: ◦ References, rename ◦ More diagnostics (lint, custom, etc.)
76. gopls is extensible • Adding new features is easier • Planned: ◦ References, rename ◦ More diagnostics (lint, custom, etc.) ◦ Quick fix suggestions
77. gopls is reliable
78. gopls is reliable • Testing framework
79. gopls is reliable • Testing framework • Go team ownership
80. gopls is reliable • Testing framework • Go team ownership • Coordination with community
81. Information To install: golang.org/wiki/gopls
82. Information To install: golang.org/wiki/gopls To contribute: golang.org/wiki/golang-tools
83. Thank you • Go team members ◦ Ian Cottrell ◦ Peter Weinberger ◦ Michael Matloob • Go community members ◦ Paul Jolly ◦ Ramya Rao ◦ Billie Cleek ◦ And many more!
87. Image credits • Gopher image by Ashley McNamara • Fire extinguisher image via strikefirstusa.com • Icons via flaticon.com, made by Freepik