Replace internal IActivationFactory
definition with tailored definition
#1678
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.
The
IActivationFactory
interface is implemented by all WinRT class factories and acts as the gateway for DLL-based activation. This is a curious interface whoseActivateInstance
method isn't very practical for language projections to use since they almost always need to immediately cast the result to something other than what this method returns. As such, the definition used by thewindows
crate is different to the one provided by the generated bindings. In order to avoid name collisions, the version used internally by the factory cache is renamed to avoid this conflict. #1675 should also help to avoid such collisions in a more general way in future but is a bigger change that I'll tackle separately.This PR also updates the test component to illustrate how components can implement
IActivationFactory
directly using the bindings generated by thebindgen
crate rather than depending on the internal definition used by thewindows
crate.Fixes #1662