Skip to content

Conversation

@mpetruska
Copy link
Contributor

work in progress...

Fixes issue #629.


Note: contains the changes in PR #841 .

@msftclas
Copy link

msftclas commented Jan 2, 2016

Hi @mpetruska, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!

The agreement was validated by Microsoft and real humans are currently evaluating your PR.

TTYL, MSBOT;

@mpetruska
Copy link
Contributor Author

Currently the missing name resolutions are fixed:
intellisense_screenshot

A type constraint error occurs when the type checker tries to unify types unit and 'a list, after which type inference is not run to specialize List.map, hence the type of the function parameter (abcd) is left as 'a.

Further work is needed to try to infer the types for IntelliSense.

Copy link
Contributor Author

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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's totally ok

@dsyme
Copy link
Contributor

dsyme commented Jan 5, 2016

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.

@mpetruska
Copy link
Contributor Author

Unfortunately I'm having some trouble with the IDE unit tests.

Running the IDE tests (RunTests.cmd debug ideunit) without the changes gives the following results:

Tests run: 4146, Passed: 3289, Errors: 154, Failures: 703, Inconclusive: 0

With my changes the result is:

Tests run: 4149, Passed: 3292, Errors: 154, Failures: 703, Inconclusive: 0

In my opinion the type inference problem (see above) can be solved, will continue to work on it.

@enricosada
Copy link
Contributor

@mpetruska what are the ideunit failures?

@mpetruska
Copy link
Contributor Author

@enricosada
Here is the log of the test run without the changes: IDEUnit_Output_base.log.txt
Here is the one that contain my changes: IDEUnit_Output_withchanges.log.txt

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).

@KevinRansom
Copy link
Contributor

@mpetruska Hi, how is this PR progressing? should I close it, or is it ready for review?

@mpetruska
Copy link
Contributor Author

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.

@KevinRansom
Copy link
Contributor

KevinRansom commented Aug 21, 2016

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

@KevinRansom
Copy link
Contributor

Closing

@KevinRansom KevinRansom closed this Nov 8, 2016
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