SearchApi.IQuerySolution.Resolve() should not require unsafe pointer for parameter "SYSTEMTIME* pstReferenceTime" about vanara HOT 7 CLOSED

The parameter notes for pstReferenceTime indicate

A pointer to a SYSTEMTIME value to use as the reference date and time. A null pointer can be passed if sqro is set to SQRO_DONT_RESOLVE_DATETIME.
The 3.4.17 version couldn't allow for that so that prompted the change.

Can you help me understand more about your comment "Also unsafe code will break the IAsynEnumerable pattern."? Do you mean that you have to then have unsafe blocks? If that is the case, I can overloads that support both options in Vanara so you can just use safe code.

from vanara.

Yes, better provide a overload for that because it's not possible to create a *variable (unsafe pointer) without enabling unsafe switch for C#. For the code in 4.0.0, it's no possible to use fully safe pointer if you defined something *parameter instead of IntPtr

from vanara.

The parameter notes for pstReferenceTime indicate

A pointer to a SYSTEMTIME value to use as the reference date and time. A null pointer can be passed if sqro is set to SQRO_DONT_RESOLVE_DATETIME.

The 3.4.17 version couldn't allow for that so that prompted the change.

Can you help me understand more about your comment "Also unsafe code will break the IAsynEnumerable pattern."? Do you mean that you have to then have unsafe blocks? If that is the case, I can overloads that support both options in Vanara so you can just use safe code.

If you try to use unsafe code in a function that returns IAsyncEnumerable. You will get an error from the compiler: "Unsafe code may not appear in iterators"

from vanara.

FYR: C# Compiler Error CS1629

from vanara.

Thank you. I'll dig into this and find a resolution.

from vanara.

Fixed in 4.0.1

from vanara.

Thanks, and hope will release 4.0.1 soon~

from vanara.