Skip to content

Integrate from fsharp\fsharp master #641

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

Merged
merged 431 commits into from
Oct 12, 2016
Merged

Integrate from fsharp\fsharp master #641

merged 431 commits into from
Oct 12, 2016

Conversation

dsyme
Copy link
Contributor

@dsyme dsyme commented Sep 28, 2016

No description provided.

jackmott and others added 30 commits August 10, 2016 21:11
1.  Use public sign.
2.  fix some slightly irritating indentation.
3. Move release and debug speciffic settings to settings.targets
4. Remove TargetFramework support for platforms that are not part of the OSS build.
mrinaldi and others added 15 commits September 20, 2016 09:24
* Cleanup Optimizer
Thank you for taking care of this.
* We don't need to check the lenght here

* Don't convert list to array multiple times

* Only fold the Flatlist

* Optimize FlatList away

* Revert code duplication

* match => if

* cleanup

* DevirtualizeApplication doesn't need optimized Expression
Integrate Microsoft/visualfsharp --> master
@dsyme
Copy link
Contributor Author

dsyme commented Oct 11, 2016

@ncave @enricosada This integration busts the .NET Core support. I'm trying to work through the issues (first time I've looked closely at FCS support for .NET Core)

@ncave
Copy link
Contributor

ncave commented Oct 11, 2016

@dsyme I don't see any errors when I run build RunTests.NetCore on your branch, also no errors after your branch is merged with master.

@7sharp9
Copy link
Member

7sharp9 commented Oct 11, 2016

Last time I had mono and dnc installed at once it didn't compile.

@ncave
Copy link
Contributor

ncave commented Oct 11, 2016

The most recent FCS builds seem to have some issue with mono:latest (FSharp.Core reference missing, from briefly inspecting the Travis logs), but it may or may not be a different issue. My local mono version is 4.2.3, dnc is 1.0.1 and merged integrate-776 build fine and tests are ok.

tl;dr I don't know what's wrong, works on my machine :-|

@dsyme
Copy link
Contributor Author

dsyme commented Oct 11, 2016

@ncave I pushed a fix - there was some internal caching behaving incorrectly. One test fails - something to do with multiple StringBuilder types

The way we have to scrape the sample project in tests...\Common.fs for a list of default reference assemblies for scripts (and just to get off the ground for projects) is awkward. I suppose we'll have to bake that list into the compiler DLL or synthesize it via another technique

@dsyme
Copy link
Contributor Author

dsyme commented Oct 11, 2016

The most recent FCS builds seem to have some issue with mono:latest (FSharp.Core reference missing, from briefly inspecting the Travis logs), but it may or may not be a different issue.

Yes. This is a different issue though. We need to fix it...

@dsyme
Copy link
Contributor Author

dsyme commented Oct 11, 2016

@ncave I fixed the problem with that .NET Core test I had to disable, and also enabled a few more .NET Core tests, see e904062

@dsyme dsyme merged commit c494a9c into fsharp:master Oct 12, 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.