Skip to content

Conversation

@jkoritzinsky
Copy link
Member

Make the cdac APIs public but experimental to make them easier to experiment with in other projects while we are still stabilizing the API surface.

Any usages outside of the cdac folder (or outside the repo entirely) will need to actively opt-in to using these APIs by suppressing the warning from the Experimental attribute.

Also address feedback from analyzers that kicked in as soon as I removed all of the IVT attributes. Keep the IVT for the tests though as they use a lot of "internal" types.

I've tried to limit the public API surface to the contract abstractions and the contract factories, at least as a starting baseline. I did make public all types used in the SOS-Dac interface implementation.

@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

@jkoritzinsky jkoritzinsky merged commit d9b7515 into dotnet:main Jan 29, 2025
146 of 150 checks passed
@jkoritzinsky jkoritzinsky deleted the experimental-cdac-apis branch January 29, 2025 04:24
grendello added a commit to grendello/runtime that referenced this pull request Jan 30, 2025
* main:
  Make cdac APIs public but experimental (dotnet#111180)
  JIT: Enable inlining for late devirtualization (dotnet#110827)
  Remove unsafe `bool` casts (dotnet#111024)
  Fix shimmed implementation of TryGetHashAndReset to handle HMAC.
@github-actions github-actions bot locked and limited conversation to collaborators Feb 28, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants