Intrinsics declared with wrong arg count ICE about rust HOT 5 CLOSED

Copying from #123526 (comment):

we [should] introduce a new, separate, version of panicking that doesn't "look" like an ICE but rather a generic "invalid language state" error that stops the compilation, with no stack trace.

I think this ticket is a good example of a case where having a distinction between "the compiler made a mistake" and "the user modifiable language state is incorrect" in the panic output would be useful. It'd be already great if it only applied to the "expect" methods (like "assume the Sized trait is available" methods). If those weren't an automatic ICE, I think we could clean up rustc code a bunch.

from rust.

i think we should just make the ICE message here a bit clearer
keep the stack trace or whatever but mention way more clearly that internal features are not supported and that if the ICE is related to that, that we don't want a bug report.

from rust.

note: using internal features is not supported and expected to cause internal compiler errors when used incorrectly

It's a bit hidden in the ICE message, understandable that you've missed it.

from rust.

Oh. I should've seen that. Thanks :)

from rust.

You could replace all of the bugs with that but you can't replace things like indexing with it without making the compiler code uglier. I am not sure where rustc could be cleaned up by making this code less panicky... if there's anything that would be cleaner in the compiler code without panicking then please just do that today!

from rust.