activation condition WARN in v3.3

Cantor, Scott cantor.2 at osu.edu
Wed Feb 1 20:18:41 EST 2017


On 2/1/17, 8:05 PM, "users on behalf of Andrew Morgan" <users-bounces at shibboleth.net on behalf of morgan at orst.edu> wrote:

> Is there some new way to specify this in v3.3? 

Somebody asked about this already, and I believe under a debugger I concluded that when this happens it's actually attempting the conversion first, and only after that point does it see that the other constructor is the better one to use.

so it probably isn't entirely accurate but the only way to get rid of the warning is to just be explicit. It might work to actually add a type indicator to the argument, but normally you just do it by naming the constructor argument (candidates).

-- Scott




More information about the users mailing list