Internal error in runtime when testing Polyhedra.jl

[KristofferC]

https://s3.amazonaws.com/julialang-reports/nanosoldier/pkgeval/by_hash/f51f24c_vs_2ca8b0c/Polyhedra.primary.log

Internal error: encountered unexpected error in runtime:
MethodError(f=Base.string, args=(Expr(:call, :==, Expr(:call, :length, :aparams), Expr(:call, :length, :mparams)),), world=0x000000000000124a)
jl_method_error_bare at /workspace/srcdir/src/gf.c:1851
jl_method_error at /workspace/srcdir/src/gf.c:1869
jl_lookup_generic_ at /workspace/srcdir/src/gf.c:2494 [inlined]
ijl_apply_generic at /workspace/srcdir/src/gf.c:2509
macro expansion at ./error.jl:231 [inlined]
ir_inline_unionsplit! at ./compiler/ssair/inlining.jl:483
batch_inline! at ./compiler/ssair/inlining.jl:617
ssa_inlining_pass! at ./compiler/ssair/inlining.jl:85
jfptr_ssa_inlining_passNOT._15640.clone_1 at /opt/julia/lib/julia/sys.so (unknown line)
_jl_invoke at /workspace/srcdir/src/gf.c:2331 [inlined]
ijl_apply_generic at /workspace/srcdir/src/gf.c:2513
run_passes at ./compiler/optimize.jl:514
optimize at ./compiler/optimize.jl:505 [inlined]
_typeinf at ./compiler/typeinfer.jl:253
typeinf at ./compiler/typeinfer.jl:209
typeinf_edge at ./compiler/typeinfer.jl:856
abstract_call_method at ./compiler/abstractinterpretation.jl:593
abstract_call_gf_by_type at ./compiler/abstractinterpretation.jl:132
abstract_call_known at ./compiler/abstractinterpretation.jl:1593
...

Seems to error here:

julia/base/compiler/ssair/inlining.jl

Line 483 in 2db86f2

@assert length(aparams) == length(mparams)

[KristofferC]

Also happens for LazySets: https://s3.amazonaws.com/julialang-reports/nanosoldier/pkgeval/by_hash/f51f24c_vs_2ca8b0c/LazySets.primary.log

[vtjnash]

Added by ce70402, though I don't know why it would be making an assumption like that.

[ianatol]

MWE for the Polyhedra one:

using Polyhedra
v = convexhull([1, 0, 0]) + conichull(Ray([0, 1, 0]), Line([0, 0, 1]))

[vtjnash]

It looks like these packages defines some unnecessarily complicated Union types, which probably hurts there performance quite a lot (e.g. Polyhedra.It). But we should be able to keep it from printing an internal error.