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

initial version of completion for named parameters #220

Closed
wants to merge 4 commits into from

Conversation

vladima
Copy link
Contributor

@vladima vladima commented Feb 7, 2015

This PR tracks the work of adding completion for named parameters\settable properties in methods.
Pending work: add tests
parametercompletion

@forki
Copy link
Contributor

forki commented Feb 7, 2015

Wow. Very cool

@enricosada
Copy link
Contributor

I dont understand Anchor. Is shown because is a setter property of the return value of MakeForm?

@vladima
Copy link
Contributor Author

vladima commented Feb 9, 2015

@enricosada yes, this is correct. In F# named argment syntax can be used to specify value of the input parameter and settable property\field on the return value

@dsyme
Copy link
Contributor

dsyme commented Feb 9, 2015

The code looks great - wonderful to see this drop out reasonably smoothly.

Looking forward to the tests :)

@dsyme
Copy link
Contributor

dsyme commented Feb 13, 2015

This is awesome

The one extra thing I'd like for both parameters and settable fields is to pin down what happens when the trailing ")" is removed - e.g.

  • if there is whitespace to end-of-line and then nothing
  • if there is whitespace to end-of-line and then another "let" at the start of the next line
  • if there is whitespace to end-of-line and then another "type" at the next un-indented position on the next line

I'm not too concerned if we don't give perfect results in these scenarios, but I'd really like to pin down what does/doesn't work to make sure we know if we regress something in the future.

This extra testing ould be added as a separate PR though.

thanks!
don

@vladima
Copy link
Contributor Author

vladima commented Feb 13, 2015

Yes, I'll add a separate PR with tests for broken code

@latkin
Copy link
Contributor

latkin commented Feb 13, 2015

This results in additional errors being output in test fsharp\typecheck\sigs\neg61.fs (tests negative cases for query expressions). Can you take a look?

@vladima
Copy link
Contributor Author

vladima commented Feb 13, 2015

@latkin, good catch - I've updated the code

@latkin latkin closed this in b9d2f3f Feb 17, 2015
@latkin latkin added the fixed label Feb 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants