Not instantiating an abstract class is fine; that's a very sensible
restriction. Catching non-abstract class methods in this same net? That's a
bit less understandable.
Adding a unit test to demonstrate this problem. It was encountered while
trying to port some real-world code to Smart Mobile Studio, so hopefully a fix
can get in in time for the 2.1 release.
Original issue reported on code.google.com by masonwhe...@gmail.com on 3 Jul 2014 at 1:03
Original issue reported on code.google.com by
masonwhe...@gmail.com
on 3 Jul 2014 at 1:03