In every conforming implementation I've seen for IVector, when the vector contents are modified, it will invalidate all previously obtained views (IVectorView) and iterators (IIterator), causing them to return E_CHANGED_STATE on subsequent operations.
This HRESULT is projected as:
winrt::error_changed_state in C++/WinRT
Platform::ChangedStateException in C++/CX
System.InvalidOperationException in .NET/C#
It would be extremely helpful to note this as the typical behavior, as well as providing guidance for implementers.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 373e61cf-6eb1-6908-0f87-1fb25449fbed
Version Independent ID: d2c31fce-5750-c7fd-4fa4-f28bcb202b6f
ChrisGuzak
commented
4 years ago
In every conforming implementation I've seen for
IVector, when the vector contents are modified, it will invalidate all previously obtained views (IVectorView) and iterators (IIterator), causing them to returnE_CHANGED_STATEon subsequent operations.This
HRESULTis projected as:winrt::error_changed_statein C++/WinRTPlatform::ChangedStateExceptionin C++/CXSystem.InvalidOperationExceptionin .NET/C#It would be extremely helpful to note this as the typical behavior, as well as providing guidance for implementers.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.