PythonYunfei

`?` allow `unset` to be passed instead of potential throwing. If the code will always work without throw, then I think warning is incorrect and unnecessary.

> I think I misunderstood what your code did... > > You are using the `throw` function incorrectly. Let's forget `throw`, it's used just for example. I unproperly use `throw`...

> there is no warning here (added `()` around), it's not a bug with `?` or `??` By the way, I would like to suggest the below code which has...

https://github.com/thqby/vscode-autohotkey2-lsp/issues/221 : @RaptorX Do you know when and why the warning was introduced? What's the real and original purpose of the idea of the warning? If without V2.1, it will...

I have known your point. Worrying for `""` in your point will be another feature request, which has not been posted by someone yet, before #221 or after #221. Perhaps...

This feature serves on #221, doesn't it? Therefore, at least, I would like to suggest the warning to be suppressed by `?`. It's in the intention of Lexikos who posted...

Yes, I mean `no_return()?`, the latter, which is what I wished to be supported. After all, `f()?` will be used more and more frequently in version 2.1.

Still. And sorry if offend： > and would mask the problems presented by https://github.com/thqby/vscode-autohotkey2-lsp/issues/221. The only problem presented by #221 is that existing codes like `=>fff()` without `?` will throw...

We are just using sentences which contain the same word "nothing", to express two different kinds of meanings.

@thqby Maybe the named pipe instance i.e. `A_ScriptFullPath`, has not been created before a call to `FileOpen`. You might need to call `WaitNamedPipe` to wait for the named pipe instance...