IWbemLocator::ConnectServer API signature change breaks nullable BSTR parameters in v0.59

[takanara1994]

Summary

v 0.58

windows::Win32::System::Wmi::IWbemLocator
pub unsafe fn ConnectServer<P0, P1, P2, P3, P4, P5>(&self, strnetworkresource: P0, struser: P1, strpassword: P2, strlocale: P3, lsecurityflags: i32, strauthority: P4, pctx: P5) -> windows_core::Result<IWbemServices>
where
    P0: windows_core::Param<windows_core::BSTR>,
    P1: windows_core::Param<windows_core::BSTR>,
    P2: windows_core::Param<windows_core::BSTR>,
    P3: windows_core::Param<windows_core::BSTR>,
    P4: windows_core::Param<windows_core::BSTR>,
    P5: windows_core::Param<IWbemContext>,

v 0.59

pub unsafe fn ConnectServer<P6>(&self, strnetworkresource: &windows_core::BSTR, struser: &windows_core::BSTR, strpassword: &windows_core::BSTR, strlocale: &windows_core::BSTR, lsecurityflags: i32, strauthority: &windows_core::BSTR, pctx: P6) -> windows_core::Result<IWbemServices>
where
    P6: windows_core::Param<IWbemContext>,

struser,strpassword,strlocale,strauthority nullable?

[tim-weis]

You can pass BSTR::new() or BSTR::default(). The BSTR value returned from either function is equivalent to a null pointer in C or C++.

[kennykerr]

Right, I alluded to that here: #3359 (comment)

The BSTR type was mistakenly considered nullable/optional by previous version of windows-bindgen. That has been fixed and mainly means that you can't use None in place of an empty BSTR. 8b10d63

[kennykerr]

Here's an example: https://github.com/microsoft/windows-rs/blob/master/crates/samples/windows/wmi/src/main.rs

[takanara1994]

thank you all guys reply.