Anh-Dung Phan

> F12 should always jump to implementation (currently it jumps to function implementation and to type signature (fsi)) Could you elaborate on this? > 1. If we are in FSI...

Sounds reasonable. Implementing this means overriding Visual F# tool's F12 completely. Are you fine with that? An alternative is to have a new command (e.g. Alt Shift F12) to switch...

You're right. I made an attempt here https://github.com/dungpa/PowerTools/tree/f12, but it obviously doesn't work since ImplementationLocation and SignatureLocation often point the same location.

Reported upstream.

I need help to choose a proposal. It's not obvious which one is better at the moment.

The idea is as follows: 1. Right click on an F# file in Solution Explorer, click "Generate signature file for the implementation file" 2. If the sig file exists, ask...

To be honest, my expectation is low on this matter. I hope to implement this feature so that we can use it on VFPT and make long-term maintenance of the...

@CodEFouR @mastoj Could you try the workaround described at https://github.com/jaredpar/VsVim/issues/1804#issuecomment-230495041? It seems like a bug of Visual Studio itself.

Yes, fully qualified names seem better. I don't recall why we use short names; maybe @vasily-kirichenko remembers the reason :-).

I think using `open A` might be wrong in some cases if there are multiple `A` modules from different namespaces. But we don't yet see any bug related to this;...