-
Notifications
You must be signed in to change notification settings - Fork 842
[WIP] Fix for missing IntelliSense after type constraint error #848
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
Conversation
|
Hi @mpetruska, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution! The agreement was validated by Microsoft and real humans are currently evaluating your PR. TTYL, MSBOT; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This unfortunately hurts performance, but only in case an error occurs in UnifyTypes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's totally ok
|
Interesting fix. I believe I've seen other manifestations of this problem. Does the change pass all the IDE nunit tests? If you could add a new IDE unit test that would be great. |
|
Unfortunately I'm having some trouble with the IDE unit tests. Running the IDE tests ( With my changes the result is: In my opinion the type inference problem (see above) can be solved, will continue to work on it. |
|
@mpetruska what are the ideunit failures? |
|
@enricosada I checked a couple of failures manually (only IntelliSense ones), they seemed to work correctly in Visual Studio 2015. I think there's some configuration issue on my box, I'm using Windows 8.1 and the Community edition of VS 2015 (Version 14.0.24720.00 Update 1, .Net 4.6). |
|
@mpetruska Hi, how is this PR progressing? should I close it, or is it ready for review? |
|
Hi @KevinRansom, sorry for the late reply, unfortunately I could not find time to update this one. Also I think the code is so out-of-date, that it's better to close it. |
|
I will keep it around, and maybe someone will have the time to pick it up. and thank you for taking the time to get this started. Kevin |
|
Closing |

work in progress...
Fixes issue #629.
Note: contains the changes in PR #841 .