@@ -35,7 +35,7 @@ let ``Intro test`` () =
35
35
let inputLines = input.Split( '\n' )
36
36
let file = " /home/user/Test.fsx"
37
37
let untyped , typeCheckResults = parseAndTypeCheckFileInProject( file, input)
38
- let identToken = Parser.tagOfToken ( Parser.token. IDENT( " " ))
38
+ let identToken = FSharpTokenTag. IDENT
39
39
40
40
// We only expect one reported error. However,
41
41
// on Unix, using filenames like /home/user/Test.fsx gives a second copy of all parse errors due to the
@@ -216,7 +216,7 @@ let ``Expression typing test`` () =
216
216
let inputLines = input3.Split( '\n' )
217
217
let file = " /home/user/Test.fsx"
218
218
let untyped , typeCheckResults = parseAndTypeCheckFileInProject( file, input3)
219
- let identToken = Parser.tagOfToken ( Parser.token. IDENT( " " ))
219
+ let identToken = FSharpTokenTag. IDENT
220
220
221
221
// We only expect one reported error. However,
222
222
// on Unix, using filenames like /home/user/Test.fsx gives a second copy of all parse errors due to the
@@ -239,6 +239,10 @@ let ``Expression typing test`` () =
239
239
" StartsWith" ; " Substring" ; " ToCharArray" ; " ToLower" ; " ToLowerInvariant" ;
240
240
" ToString" ; " ToUpper" ; " ToUpperInvariant" ; " Trim" ; " TrimEnd" ; " TrimStart" ])
241
241
242
+ // The underlying problem is that the parser error recovery doesn't include _any_ information for
243
+ // the incomplete member:
244
+ // member x.Test =
245
+
242
246
[<Test; Ignore( " Currently failing, see #139" ) >]
243
247
let ``Find function from member 1`` () =
244
248
let input =
0 commit comments