Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No IntelliSense for second dot of shorthand lambda syntax #18173

Open
Happypig375 opened this issue Dec 22, 2024 · 1 comment
Open

No IntelliSense for second dot of shorthand lambda syntax #18173

Happypig375 opened this issue Dec 22, 2024 · 1 comment

Comments

@Happypig375
Copy link
Member

Repro steps

Image

System.Guid()
|> _.Variant.

Expected behavior

IntelliSense completion shows.
Image

Actual behavior

No IntelliSense completion.

Known workarounds

Don't use this feature at the second dot?

Related information

Provide any related information (optional):

  • Operating system Windows
  • .NET Runtime kind (.NET Core, .NET Framework, Mono) N/A
  • Editing Tools (e.g. Visual Studio Version, Visual Studio) Visual Studio 17.12.3
@charlesroddie
Copy link
Contributor

The ability to chain properties was in the RFC https://github.com/fsharp/fslang-design/blob/main/FSharp-8.0/FS-1129-shorthand-anonymous-unary-functions.md but is an example of feature overreach. It expanded since the suggestion fsharp/fslang-suggestions#506 .

The RFC PR looks to have been improperly merged. It contains a list of additional features, including this one, which were specifically questioned by @dsyme in fsharp/fslang-design#710 with the comment "I do wonder if we should just go simple and only allow _.Foo for now". But the PR was merged anyway with no discussion of this comment.

I think everything beyond _.Foo should be treated as an unfortunate mistake.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: New
Development

No branches or pull requests

2 participants