sh03
sh03
I wonder if this is just an extension of this issue: http://stackoverflow.com/a/42632915/493122
Is your program using low level events with `abd shell getevent` and `adb shell sendevent` by any chance? Because I was about to try that to see if it was...
Maybe with C# 8 and .NET Core 3 the library could drop `NonNull` and just use C#'s `Nullable`.
> The issue I see with that is changing the default behavior from interpreting a bare reference type from being nullable to being non-nullable. That should have been the default...
I was experimenting with the idea of adding support for nullable reference types while maintaining backward compatibility and I stumbled upon this: https://stackoverflow.com/questions/56705694/how-to-detect-whether-a-type-can-be-nullable-at-runtime?noredirect=1#comment99974918_56705694 Basically nullable reference types are implemented via...
Apparently this issue is blocked by: http://github.com/dotnet/corefx/issues/38087 Once that's implemented I'll work on the non null issue myself if nobody is against it.
These days I don't have much time. Maybe next month.
@Igorbek I can't compile the entire project with nullable references because the library has to also maintain the 90% of other tests for C# 7-. By using the `#nullable` code...
> There is still no .date() or .time() method, mostly because those use cases can be trivially implemented with .regex(). @colinhacks Can they though? The trivial implementation is probably along...