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

Intellisense Tooltip get too long in case of many generic parameters #5

Closed
ilmax opened this issue Jan 15, 2015 · 5 comments · Fixed by #60545
Closed

Intellisense Tooltip get too long in case of many generic parameters #5

ilmax opened this issue Jan 15, 2015 · 5 comments · Fixed by #60545

Comments

@ilmax
Copy link

ilmax commented Jan 15, 2015

Hi, I hope to be in the right place, if not feel free to close this.

I noticed that Intellisense tool-tips become too long in case of many generic parameters with constraint, see image below.
intellisense tooltip

What I would like to see, if there are more than 1 generic constraints is to split every constraint in a new line (as you can see in generic constraint declaration on the class itself) to avoid creating a very long tool-tip and to gain readability

M.

@DustinCampbell
Copy link
Member

To be fair, this isn't a new problem. We didn't do a great job for such types in VS 2013 either:

image

The right thing to do is probably to format the type name so that the where clauses are on separate lines, which makes them easier to spot anyway.

@Pilchie Pilchie added this to the Unknown milestone Jan 16, 2015
OmarTawfik added a commit that referenced this issue May 18, 2017
* Call this.DeclaringCompilation.EnsureReadOnlyAttributeExists() when needed

* Promote EmbeddedAttribute to be used by both compilers

* Generate Embedded attributes on PE Module Builder

* Thread PEModuleBuilder through Symbol.AddSynthesizedAttributes()

* Fix failing tests

* Base case passing

* Refactor ReadOnlyAttribute to IsReadOnlyAttribute

* Fix build break

* More Tests

* Clean up

* PR Comments #1

PR Comments #3

PR Comments #4

PR Comments #5

PR Comments #6

PR Comments # 7

* Handle NoPIA

Added more tests

* Lambdas and Local functions no longer generate attributes in symbols

Added tests for constructors and operators

Signal need for synthesized attributes in local rewriter for lambdas an local functions

Clean up

* Clean up

* More PR Feedback

* Adding more tests

* More PR Comments

* More tests for explicit interface implementations

* Latest PR Comments

* Moved EnsureIsReadOnlyAttributeExists to AfterAddingTypeMembersChecks

* Fix failing tests
olegtk pushed a commit that referenced this issue Oct 16, 2018
Update fixers for execution context changes
jcouv referenced this issue in jcouv/roslyn Apr 30, 2019
jnm2 pushed a commit to jnm2/roslyn that referenced this issue Dec 8, 2019
CyrusNajmabadi pushed a commit that referenced this issue Jul 31, 2020
@RenderMichael
Copy link
Contributor

Unfortunately this is still exactly unchanged.

 
Image

@CyrusNajmabadi
Copy link
Member

@RenderMichael there is a pr on this that you could help with if you're interested: #60545

@RenderMichael
Copy link
Contributor

Thanks @CyrusNajmabadi ! The uptake process for me would probably take longer than the actual PR, depending on how involved it was.

Congrats on closing one of the oldest issues in the repo 🎉

@ilmax
Copy link
Author

ilmax commented Nov 13, 2024

Thank you for fixing this one 🎉🎉

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

Successfully merging a pull request may close this issue.

7 participants