Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
API Request: TypeSymbolExtensions
See original GitHub issueForking this feature request from #16
Original post: https://github.com/dotnet/roslyn/issues/16#issuecomment-70846421 by @MrJul
Pertinent APIs: http://source.roslyn.codeplex.com/#Microsoft.CodeAnalysis.CSharp/Symbols/TypeSymbolExtensions.cs,8f632696b9da5eba
In my team, I’ve seen different developers copy-paste portions of ITypeSymbolExtensions into our own project (e.g. IsNullableType, GetNullableUnderlyingType , GetBaseTypes ), which is a shame - these methods are a convenience I’m sure many other people will find useful as well.
Issue Analytics
- State:
- Created 9 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
any progress on this?
A request for this should go through our “api proposal” path. Note that these APIs are unlikely to be exposed as they are really ‘feature-level’ apis that encode feature semantics and change as necessary. As a public API we would be unable to do that as it would likely break people (or every change would need some way to make it opt-in only, which would greatly increase complexity).