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

Cross target NET472 and enable extended intrinsics behind symbol #746

Merged
merged 3 commits into from
Oct 24, 2018
Merged

Conversation

iamcarbon
Copy link
Contributor

@iamcarbon iamcarbon commented Oct 24, 2018

Prerequisites

  • I have written a descriptive pull-request title
  • I have verified that there are no overlapping pull-requests open
  • I have verified that I am following matches the existing coding patterns and practice as demonstrated in the repository. These follow strict Stylecop rules 👮.
  • I have provided test coverage for my change (where applicable)

Description

This PR cross targets NET472 and introduces a SUPPORTS_EXTENDED_INTRINSICS symbol to enable the new extended intrinsics support on modern runtimes (NET472+ & NETCOREAPP2.1+).

This PR also retarget the NET471 tests to NET472. Extended tests continue to run against NET471.

@iamcarbon iamcarbon mentioned this pull request Oct 24, 2018
5 tasks
@JimBobSquarePants JimBobSquarePants merged commit cd68f80 into SixLabors:master Oct 24, 2018
@antonfirsov
Copy link
Member

@iamcarbon in my original proposal I supposed that the spannified stream API's are also available on .NET FW 4.7.2, but looks like the full unification is out of scope until .NET Standard 2.1 :(

@iamcarbon
Copy link
Contributor Author

@antonfirsov -- Yeah. :(

Even worse, their latest plan was for .NETCOREAPP3.0 to be the first runtime to implement .NETSTANDARD2.1. And it doesn't look like the desktop framework will ever implement it.

There may never be a full unification.

antonfirsov pushed a commit to antonfirsov/ImageSharp that referenced this pull request Nov 11, 2019
Cross target NET472 and enable extended intrinsics behind symbol
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.

3 participants