The code generation strategy for $deserializeLambda$ is fairly verbose, which places a relatively low limit on the number of serializable lambdas that a class can have. By "outlining" the comparison mechanics, and not using strings-in-switch, we can reduce the number of bytes per lambda, and raise the limit.