Skip to content

Conversation

@psfinaki
Copy link
Contributor

Closes #14460

Like - very basic fix but why not. WDYT?

@psfinaki psfinaki requested a review from a team as a code owner April 19, 2023 20:14
@psfinaki psfinaki merged commit ef89c69 into dotnet:main Apr 20, 2023
@T-Gro
Copy link
Member

T-Gro commented Apr 21, 2023

How can people disable just this and keep other hints?
(here "people" would include me, I do not think this is particulary useful TBH.)

CustomOperations are meant to meant nice self-describing APIs.
ParameterNames go subjectively in the way, and IMO should be enforced together with other regular parameter name hints.

@psfinaki psfinaki deleted the hints branch April 21, 2023 11:12
@psfinaki
Copy link
Contributor Author

No way for this now - created a ticket though: #15131

vzarytovskii added a commit that referenced this pull request Apr 25, 2023
Co-authored-by: vzarytovskii <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Kevin Ransom (msft) <[email protected]>
Co-authored-by: Vlad Zarytovskii <[email protected]>
Co-authored-by: Tomas Grosup <[email protected]>
Co-authored-by: Florian Verdonck <[email protected]>
Co-authored-by: Petr <[email protected]>
Co-authored-by: Petr Pokorny <[email protected]>
Fixing hints for custom ops (#15119)
Fix bug in return type hints (#15124)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

Incorrect hints for CustomOperations in a computation expression

5 participants