Fix the issue (#14334)
The problem was that we had some cached lexer state when reading new
input during FSI session. If lexer threw an error on a very first token
of new input, the cached lexer state would not get updated, so we would
assosciate old lexer state with this new token that caused an error.
Now we will invalidate that cached state at the begining of reading new
input.
Co-authored-by: NAdam Boniecki <adboniec@microsoft.com>
Showing
想要评论请 注册 或 登录