Mojo errors dropping into MLIR — how do you deal with this?

Mojo
1

I’ve been running into this with Mojo lately: something breaks, and the error drops into MLIR instead of pointing to my code.

I’m not even talking about complex stuff — just normal code that looks fine, but the error feels disconnected. At that point I’m not debugging logic anymore, just guessing what the compiler did.

I get why MLIR is there, but right now it feels like the abstraction leaks too early.

How are you dealing with this?

  • Do you just get used to reading these errors?

  • Any workflow that actually helps?

  • Or is this just where Mojo is right now?

Feels like a real DX pain for me.

2

All of those should be reported as bugs (ideally with minimal reproducers). Unless you’re doing fairly low level things (ex: touching MLIR directly) you shouldn’t see that and we treat that as one level of severity worse than the compiler segfaulting.

3

Can you give an example of what you’re seeing?