Given our raw::Variant is now raw::Variant<TS>, this isn't something we want anymore. We'll live with our own raw types, but we should probably have a feature that impls From between our and winapi's types for AutomationTypeSystem types.
We're starting to have a lot of duplication between Intercom and winapi: raw::VARIANT, raw::BSTR, etc.
Ideally we should introduce a winapi feature which pub uses the respective winapi items instead of defining our own.
This means making our own raw structs compatible with winapi and prevents us from defining custom methods on them. Instead such custom methods need to be functions or newtypes.
Fortunately in most cases we do not have that many methods on the raw types.~~
Given our
raw::Variantis nowraw::Variant<TS>, this isn't something we want anymore. We'll live with our own raw types, but we should probably have a feature that implsFrombetween our and winapi's types forAutomationTypeSystemtypes.We're starting to have a lot of duplication between Intercom and winapi:
raw::VARIANT,raw::BSTR, etc.Ideally we should introduce a
winapifeature whichpub uses the respective winapi items instead of defining our own.This means making our own raw structs compatible with winapi and prevents us from defining custom methods on them. Instead such custom methods need to be functions or newtypes.
Fortunately in most cases we do not have that many methods on the raw types.~~