This commit ( https://github.com/codecat/angelscript-mirror/commit/3599b250cb1c0df820f38e71c91c7d46338cef90 ) seemed to have broken a lot of my script bindings that relate to using ?&in
parameters. For example:
[ ScriptEngine] [12:56:25] [VehicleState] VehicleState/Debugger/Main.as (45, 2) : INFO : Compiling void TabPlayerStates()
[ ScriptEngine] [12:56:25] [VehicleState] VehicleState/Debugger/Main.as (76, 4) : ERR : Multiple matching signatures to 'UI::PushID(const wstring&)'
[ ScriptEngine] [12:56:25] [VehicleState] VehicleState/Debugger/Main.as (76, 4) : INFO : void PushID(const ?&in)
[ ScriptEngine] [12:56:25] [VehicleState] VehicleState/Debugger/Main.as (76, 4) : INFO : void PushID(const string&in id)
And:
[ ScriptEngine] [12:56:25] [PluginManager] PluginManager/src/Interface/Tabs/Plugin.as (64, 2) : INFO : Compiling void PluginTab::CheckRequestChangelog()
[ ScriptEngine] [12:56:25] [PluginManager] PluginManager/src/Interface/Tabs/Plugin.as (79, 5) : ERR : Multiple matching signatures to 'warn(Json::Value@&)'
[ ScriptEngine] [12:56:25] [PluginManager] PluginManager/src/Interface/Tabs/Plugin.as (79, 5) : INFO : void warn(const string&in)
[ ScriptEngine] [12:56:25] [PluginManager] PluginManager/src/Interface/Tabs/Plugin.as (79, 5) : INFO : void warn(?&in)
Is this a bug or an expected consequence of the change? If it's expected, is there a better way for me to handle this, or perhaps an engine property that reverts this behavior?