amp-59

I should also probably point out that the user could inspect this code and conclude that the compiler had produced undefined behaviour in order to check the sentinel value, because...

Reporting non-scalar sentinels can not work with the solution you have suggested.

@andrewrk The incompatibility with non-scalar sentinels is this: * The return type of the single function is `noreturn`. * Non-scalar sentinels require generic test code (`meta.eql`) to be compiled within...

> How about also adding an argument containing the std.builtin.SourceLocation? That is a large additional cost for common checked arithmetic operations, such as addition, subtraction, and multiplication. Each occurrence of...

@AssortedFantasy Yes, that is the current behaviour and the reason why the cost implied by the example is not realistic. It only shows one `fn_name` and `file` being reused every...

Do we make panic return `void`, make `checkNonScalarSentinel` permit override, or remove non-scalar sentinels from the language?

@wooster0 I have already completed the implementation. I am on Discord if you would like to discuss the details.

What panic do you expect from line 650 of `array_list.zig`? When I run this program I get a different source location: ``` zig run -OReleaseSafe array_list_panic.zig thread 125935 panic: mul...

> It should just tell me the correct line instead of 0. Right. But the correct source location for the panic encountered by the program you posted is in `mem.zig`....