transformations.add(new RemoveWarnings(Set.copyOf(Arrays.asList(warnings))));
    }

    /**
     * Removes one or more warnings
     *
     * @param warnings the warning(s) to remove
     * @param testName the test name to remove the warning
     */
    public void removeWarningForTest(String warnings, String testName) {
        transformations.add(new RemoveWarnings(Set.copyOf(Arrays.asList(warnings)), testName));

Our codebase uses `null` extensively to represent an absence of value or optionality of the argument.
We utilize nullness annotations in Java code and somewhat rely on IDE warnings to guide us.
However, the Java code we have is not fully annotated, which causes several consequences:
* IDE warnings can be misleading
* Redundant null checks may increase binary size, hurt performance, and increase cognitive load for readers

    private final Set<String> warnings;
    private String testName;

    /**
     * @param warnings The allowed warnings to inject
     */
    public RemoveWarnings(Set<String> warnings) {
        this.warnings = warnings;
    }
    /**
     * @param warnings The allowed warnings to inject
     * @param testName The testName to inject
     */

                if (!errors.contains(req.getMessage())) {
                    errors.add(req.getMessage());
                }
                break;
            case WARNING:
                if (!warnings.contains(req.getMessage())) {
                    warnings.add(req.getMessage());
                }
                break;
            default:
                throw new IllegalArgumentException("Unknown severity: " + req.getSeverity());

                warnings << "Return nullability changed from nullable to null-unmarked"
            }
        }

        if (!errors.isEmpty()) {
            def changes = errors + warnings
            return acceptOrReject(member, changes, Violation.error(member, changes.join(" ")))
        }
        if (!warnings.isEmpty()) {
            return Violation.warning(member, warnings.join(" "))
        }

# Ignore arch dependent warnings, we chose the right libs on start
fess binary: arch-independent-package-contains-binary-or-object
# Not stripping external libraries
fess binary: unstripped-binary-or-object
# Ignore arch dependent warnings, we chose the right libs on start
fess binary: arch-dependent-file-in-usr-share
# Please check our changelog at https://github.com/codelibs/fess

 */
@Deprecated(since = "4.0.0")
public class Result<T> {

    /**
     * Success without warnings
     *
     * @param model
     */
    public static <T> Result<T> success(T model) {
        return success(model, Collections.emptyList());
    }

    /**
     * Success with warnings
     *
     * @param model
     * @param problems
     */

    val errors: List<ReportMessage>,
    val warnings: List<ReportMessage>,
    val information: List<ReportMessage>,
    val accepted: List<ReportMessage>
) {

    val isEmpty: Boolean
        get() = errors.isEmpty() && warnings.isEmpty() && information.isEmpty()

    fun toText() =
        StringBuilder("Binary compatibility\n").apply {

            }
            if (false == warnings.isEmpty()) {
                current.println("      warnings:")
                for (String warning in warnings) {
                    // Escape " because we're going to quote the warning
                    String escaped = warning.replaceAll('"', '\\\\"')
                    /* Quote the warning in case it starts with [ which makes

# org.eclipse.jdt.core.compiler.problem.nullAnnotationInferenceConflict=warning
# org.eclipse.jdt.core.compiler.problem.nullReference=warning
# org.eclipse.jdt.core.compiler.problem.nullSpecViolation=warning
# org.eclipse.jdt.core.compiler.problem.nullUncheckedConversion=warning
# org.eclipse.jdt.core.compiler.problem.potentialNullReference=warning