Phillip Carter
Phillip Carter
We can, yeah. There is already a library author guidance guide here: https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/ So the F# docs would not be a bad choice.
docs.microsoft.com does this for a few reasons: * Examples can be larger, and pages shouldn't be too massive in general * SEO for specific things can kick in * Realistically...
Those were the old MSDN samples. Most are pretty good. They're fairly comprehensive as well, so we're not starting from 0 in terms of examples. But they need to be...
This would have to be a feature in FSharp.Formatting: https://github.com/fsprojects/FSharp.Formatting
That'd be grand!
Yeah, this is not much of a deal IMO. They're usually very little changes in fsharp.core from release to release, and even if there was a substantial change, the vast...
Yeah, I think it would be great to any new APIs in FSHarp.Core require complete XML docs.
Dunno if this is relevant, but in debugging, I noticed that [this line](https://github.com/Microsoft/visualfsharp/blob/master/src/fsharp/tast.fs#L4794) gets hit four times on `ThisIsAProperty` has a match, when document highlight hits it twice. I'll probably...
@isaacabraham Can you be specific about which constructs this fails on? This works fine in scripts for functions, F# types, F# class names, etc. But fails for members, modules, and...
In a hive of VS, Find all References works for properties, but outside of that hive, it doesn't. Rename fails, though.