mirror of
https://github.com/golang/go
synced 2024-11-18 22:55:23 -07:00
825cb06263
Having nil ranked normally causes it to show up as the top candidate in cases like: context.WithCancel(<>) // "nil" shows up before "context.Background()" "context.Background()" gets a slight score penalty since it is a deep completion, so "nil" is ranked highest. Sometimes you do want "nil", but it's such a short identifier you probably aren't leaning too heavily on autocompletion. I think it makes sense to optimize for the case when you want something non-nil. Change-Id: I537927db2b573535e751380c4cba5c9873dfe524 Reviewed-on: https://go-review.googlesource.com/c/tools/+/210539 Run-TryBot: Muir Manders <muir@mnd.rs> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Rebecca Stambler <rstambler@golang.org> |
||
---|---|---|
.. | ||
comment_test.go | ||
comment.go | ||
completion_format.go | ||
completion_keywords.go | ||
completion_labels.go | ||
completion_literal.go | ||
completion_snippet.go | ||
completion.go | ||
deep_completion.go | ||
diagnostics.go | ||
errors.go | ||
folding_range.go | ||
format.go | ||
highlight.go | ||
hover.go | ||
identifier.go | ||
implementation.go | ||
options.go | ||
references.go | ||
rename_check.go | ||
rename.go | ||
signature_help.go | ||
source_test.go | ||
suggested_fix.go | ||
symbols.go | ||
tidy.go | ||
util.go | ||
view.go |