All CLA requirements met.

@gusty is there a language suggestion change that maps to this? Generally I'm in favor.

Another interesting one (if you're digging around in there) isfor __ in do:

Error message kinda sucks, and the resolution is a double_.

Yes, it's approved in principle, seefsharp/fslang-suggestions#333

I've never thought about thefor _ in, I will dig into it, in aseparate PR.

@gusty Thanks!

Thanks a lot for trying to take care of this wart ;)

Note: this code fixer can also be changed with this PR:https://github.com/dotnet/fsharp/blob/master/vsintegration/src/FSharp.Editor/CodeFix/RenameUnusedValue.fs#L73

Actually for the renamer you suggested it won't cause problems. I was thinking in the warning mechanisms. For the identifiers starting with underscore it won't be a problem, but for existingmember x. we could issue a warning once this feature is added, but as I said it would be sort of a breaking change.

I had a look at how it works right now and it already considers unused bindings everything that doesn't start with an underscore, so we're good to change the renamer too.

@cartermp I adjusted the renamer, as you suggested.

targeting fsharp47

Love this update, however I noticed that it doesn't work with an accessibility modifier:

type MyType =    { Hello : string }    member private __.WorldOk = "World ok"    member private _.WorldOhNo = "World not ok"

Do you want me to open a separate issue?

Good catch !

I've just added a PR (#7631) that will cover that case.