Muir Manders 3d643c64ae internal/lsp: add literal completion candidates ... Add support for literal completion candidates such as "[]int{}" or "make([]int, 0)". We support both named and unnamed types. I used the existing type matching logic, so, for example, if the expected type is an interface, we will suggest literal candidates that implement the interface. The literal candidates have a lower score than normal matching candidates, so they shouldn't be disruptive in cases where you don't want a literal candidate. This commit adds support for slice, array, struct, map, and channel literal candidates since they are pretty similar. Functions will be supported in a subsequent commit. I also added support for setting a snippet's final tab stop. This is useful if you want the cursor to end up somewhere other than the character after the snippet. Change-Id: Id3b74260fff4d61703989b422267021b00cec005 Reviewed-on: https://go-review.googlesource.com/c/tools/+/193698 Run-TryBot: Rebecca Stambler <rstambler@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Rebecca Stambler <rstambler@golang.org>		2019-09-18 17:13:17 +00:00
..
snippet_builder_test.go	internal/lsp: add literal completion candidates	2019-09-18 17:13:17 +00:00
snippet_builder.go	internal/lsp: add literal completion candidates	2019-09-18 17:13:17 +00:00