Lucas Teixeira

Today **where** is restrictive, not allowing the code to compile in case the condition isn't meet. The reuse of the **where** keyword would force the caller to check the parameters?...

@Lexcess, To be honest, I'm not sure! I like the idea of **where** begin reused, as no new keywords need to be created and it has this logical sense of...

@Serg046, In this case, it would have to be changed to a runtime exception or GetValueFromDb have the check applied to its return value - the same process we need...

@NickCraver I don't think using Options as static is a good thing. Someone might need to connect to two different databases at the same time using two different mapping schemes,...

@NickCraver I haven't seen the big picture. All alternatives I could think of after your explanation would do more harm than good.

@rhishikesh-helpshift Can you check your .csproj to see if the reference to the Xamarin.Swift project is in there on the final iOS app project?

@Macjon @kaysho just pushed version 1.0.10, please check if it fixes the problem for you.

@kaysho I realized that 1.0.10 allowed the app to compile, but broke the library actual function. I've just sent a new update to fix it.

Thanks for reporting this @shrop21 . It is about time to update the binding to the latest version of the library. I know this issue is very old, but for...

@nininea1 what is your minimum iOS target? Is that 12.2 and above or lower? Can you upgrade to Xamarin.Swift 1.0.4? You are using 1.0.2 and there were some bug fixes...