sync up branch pointers #902
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Correct paths to vsix
This was missed in #5890
* Checking assembly when checking for String.Concat in Optimizer * Don't call TypeRef directly as we don't know if it's a nominal type
* Always emit conditional attributes in FCS (fixes #3890) * Add test * Cleanup test * Add internal compiler switch, emit conditional method calls * Update test * Make noConditionalErasure lowercase
Merge dev15.9 to master
Merge dev15.9 to dev16.0
* chunkify TcSymbolUseData * move LOH size out to a constant * do chunking and mapping together to reduce allocations * clarify comment around GC impacts * add comment informing others of the potential for LOH allocations
* add some docs * more docs * more docs * more docs/spacing * more docs/spacing * more docs/spacing
save and publish log from package publishing step
save and publish log from package publishing step
This reverts commit 49c1bbb.
Merge dev16.0 to dev16.1
* Update FSharp.Core package to 4.6.1, Fix product version (* AssemblyVersion of compiler binaries *) and remove trailing '.' from githash. * Update ci_part4 * signtool data * address test
Merge dev16.0 to dev16.1
There is no need for the Xamarin workload nor the net472 component. .NET Framework 4.7.2 is installed by default with VS 2019 now.
* Enable pinvoke tests for coreclr * Update Build.ps1
* Add VSConfig file * Trim it
* comment state machine compilation * add signature file * add signature files
* remove redundant code * remove redundant code
* Consolidate lots of info * Add a quickstart so folks don't need to open the devguide for basic build/dev * Remove lots of info that isn't about this repository at all
Co-Authored-By: cartermp <[email protected]>
* Update dependencies from https://github.com/dotnet/arcade build 20190418.4 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19218.4 * Update dependencies from https://github.com/dotnet/arcade build 20190418.7 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19218.7 * Update dependencies from https://github.com/dotnet/arcade build 20190422.2 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19222.2 * Update dependencies from https://github.com/dotnet/arcade build 20190423.2 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19223.2 * Update dependencies from https://github.com/dotnet/arcade build 20190424.9 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19224.9 * Update dependencies from https://github.com/dotnet/arcade build 20190425.5 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19225.5 * Update dependencies from https://github.com/dotnet/arcade build 20190426.3 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19226.3
…n error messages) (#6654) * migrate (as a separate copy) fsharpqa tests that are going to be impacted by #6596 the baseline files are empty on purpose, expecting CI failure reporting those tests, I intend to update the baseline and clean up the comments / xml tags from fsharpqa syntax in later commit, and then remove those specific tests altogether from fsharpqa if this is OK with the maintainers. * update the .bsl files * remove comments that are handled by baseline files, update baseline files * remove the migrated tests from fsharpqa tests * need to be more careful when migrating those * testing if running the test with .fs instead of .fsx makes them work on .netcore * exclude migrated fsharpqa from dotnet core run
Update and simplify README
…429.8 (#6656) - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19229.8
Make readme warmer and fuzzier
…430.6 (#6661) - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19230.6
* Update dependencies from https://github.com/dotnet/arcade build 20190501.6 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19251.6 * Update dependencies from https://github.com/dotnet/arcade build 20190502.2 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19252.2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I apparently let branch pointers slip a bit here and there was some slip up between my fork and this one (and my fork was what the last release was done off of). This resyncs things and gets this repo back to being representative of the true state of things. The big file diff is because this release included the stress-testing projects.