GitLab

Check method adapter doesn't allow <init> when ldc a method handle

See merge request asm/asm!192

method handle

method handle

Fix javadoc

See merge request asm/asm!191

Resolve "Apparent regression in GeneratorAdapter.java `cast` function"

Closes #317837

See merge request asm/asm!189

Bump supported class version to V_12 (56)

See merge request asm/asm!187

Resolve "When ClassWriter copies constant pool of class reader, ClassWriter.COMPUTE_MAX does not consider changes in argument sizes"

Closes #317833

See merge request asm/asm!185

Introduces a number of methods that are called when initializing or
updating abstract values in an analyzer frame.

Before this commit, Analyzer.analyze and Frame.execute would always
call Interpreter.newValue for initializing or updating frame values.

Having multiple methods allows users to return more precise values
for the individual cases. For example, in a nullness analysis, the
initial value for the `this` parameter of an instance method can be
set to not-null.

Adds a method `setStack` to analysis.Frame which allows setting the
dataflow value of a stack slot.

Could be used in nullness analysis. After, for example, an instance call,
aliases of the receiver can be set to NotNull, both in locals and on the
stack.

Fail early when adding an instruction that already belongs to a
different instruction list.

Update the google-java-format-gradle-plugin to the latest version and reformat the source files. Due to bug https://github.com/sherter/google-java-format-gradle-plugin/issues/25 the formatting was only checked on the :asm project, and not on the other subprojects. Version 0.7 of the plugin solves this issue.

Minor Javadoc improvements

See merge request asm/asm!182