On Tue, 22 Apr 2025 23:55:54 GMT, Chen Liang wrote:
> In the future value objects JEP, class files must have one of ACC_IDENTITY
> (now ACC_SUPER), ACC_ABSTRACT, and ACC_FINAL bits set, otherwise they are
> rejected. The current default flag has none of these bits set, meaning that
> it will n
On Tue, 22 Apr 2025 23:55:54 GMT, Chen Liang wrote:
> In the future value objects JEP, class files must have one of ACC_IDENTITY
> (now ACC_SUPER), ACC_ABSTRACT, and ACC_FINAL bits set, otherwise they are
> rejected. The current default flag has none of these bits set, meaning that
> it will n
On Tue, 22 Apr 2025 23:55:54 GMT, Chen Liang wrote:
> In the future value objects JEP, class files must have one of ACC_IDENTITY
> (now ACC_SUPER), ACC_ABSTRACT, and ACC_FINAL bits set, otherwise they are
> rejected. The current default flag has none of these bits set, meaning that
> it will n
On Tue, 22 Apr 2025 23:55:54 GMT, Chen Liang wrote:
> In the future value objects JEP, class files must have one of ACC_IDENTITY
> (now ACC_SUPER), ACC_ABSTRACT, and ACC_FINAL bits set, otherwise they are
> rejected. The current default flag has none of these bits set, meaning that
> it will n
On Tue, 22 Apr 2025 23:55:54 GMT, Chen Liang wrote:
> In the future value objects JEP, class files must have one of ACC_IDENTITY
> (now ACC_SUPER), ACC_ABSTRACT, and ACC_FINAL bits set, otherwise they are
> rejected. The current default flag has none of these bits set, meaning that
> it will n
On Tue, 22 Apr 2025 23:55:54 GMT, Chen Liang wrote:
> In the future value objects JEP, class files must have one of ACC_IDENTITY
> (now ACC_SUPER), ACC_ABSTRACT, and ACC_FINAL bits set, otherwise they are
> rejected. The current default flag has none of these bits set, meaning that
> it will n
