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

Project cracking fix child references #478

Merged
merged 1 commit into from Dec 2, 2015
Merged

Project cracking fix child references #478

merged 1 commit into from Dec 2, 2015

Conversation

rneatherway
Copy link
Member

Should fix #477, depends on #476


// On some versions of Mono the referenced projects are already
// correctly included, so we make sure there aren't any duplicates
let cmdOptions = Array.ofSeq (Set.union (set parsedProject.Options)
Copy link
Contributor

Choose a reason for hiding this comment

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

Hmm.. I'd be more comfortable if

  1. keep the options in the same order and
  2. we only remove duplicates for -r options. I'm concerned that sequences like --optimize- --optimize+ --optimize- will just become --optimize- --optimize+ - I'm not sure this can really happen but it's best to avoid the possibility.

Copy link
Member Author

Choose a reason for hiding this comment

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

Very good point, adjusted significantly.

@dsyme
Copy link
Contributor

dsyme commented Dec 2, 2015

One comment - if you can fix that then we can merge. Great to see things passing.

@rneatherway
Copy link
Member Author

OK, all good.

dsyme added a commit that referenced this pull request Dec 2, 2015
…eferences

Project cracking fix child references
@dsyme dsyme merged commit 01721a1 into fsharp:master Dec 2, 2015
@dsyme
Copy link
Contributor

dsyme commented Dec 2, 2015

Great!

@rneatherway rneatherway deleted the project-cracking-fix-child-references branch December 2, 2015 11:48
@rneatherway
Copy link
Member Author

@dsyme should we go ahead and publish a new NuGet package then?

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.

Failures on Mac (Mono master) and Max/Linux (Mono 4.05)
2 participants