@@ -690,7 +690,7 @@ type TypeCheckInfo
690690// These come through as an empty plid and residue "". Otherwise we try an environment lookup
691691// and then return to the qualItems. This is because the expression typings are a little inaccurate, primarily because
692692// it appears we're getting some typings recorded for non-atomic expressions like "f x"
693- when ( match plidwith [] -> true | _ -> false ) ->
693+ when isNil plid->
694694// lookup based on expression typings successful
695695 Some( items|> List.map( CompletionItem( tryDestAppTy g ty) None), denv, m)
696696| GetPreciseCompletionListFromExprTypingsResult.NoneBecauseThereWereTypeErrors, _ ->
@@ -700,7 +700,7 @@ type TypeCheckInfo
700700| GetPreciseCompletionListFromExprTypingsResult.NoneBecauseTypecheckIsStaleAndTextChanged, _ ->
701701// we want to report no result and let second-chance intellisense kick in
702702 None
703- | _, true when ( match plidwith [] -> true | _ -> false ) ->
703+ | _, true when isNil plid->
704704// If the user just pressed '.' after an _expression_ (not a plid), it is never right to show environment-lookup top-level completions.
705705// The user might by typing quickly, and the LS didn't have an expression type right before the dot yet.
706706// Second-chance intellisense will bring up the correct list in a moment.