There’s no comments anymore…?
For mapping class mechanism, there’s no difference between java.lang.Integer and java.lang.Object, so why the former one should be disabled? “Nullable” is misunderstood here. Please just refer to bug 73822(Mapped class to wrapped value types can’t work as expected), it will make things clear.
I hope for a rollback of bugfix 73821 if there’s no quick fix for this issue.
On 8.3.92.1901, I can still write more implicit operators to avoid mapping class errors. But after bugfix 73821, I can’t do that:
(Compile error when map to normal type)
(Can’t define implicit conversion)
But I can’t just stay on 8.3.92.1901, because this issue is unresolved:
(Incorrect base method calling cause StackOverflow on Android)
Ultimately my cross-platform frameworks work has been stuck for nearly a month on these generic programming issues.
I’ve seen lots of bugfixes for Silver in recent multiple betas, but nearly nothing for problems in RO C#. I don’t think I should pay another $799 to get this.