Sukera

> In C standards and related common usage, the former is called "unspecified behavior", not undefined behavior and makes a precise distinction between them. You're right, it's unspecified behavior, not...

> This is a subtle shift in my own understanding of Julia, and I still don't quite fully appreciate why this distinction is valuable, but now I get what UB...

1.10.1 doesn't segfault for me but I still get the stackoverflow. This suggests to me that this is some canary/return address being overwritten by accident, resulting in an empty stacktrace....

rr trace is here: https://julialang-dumps.s3.amazonaws.com/reports/2024-05-24T15-42-56-Seelengrab.tar.zst

Notably, printing a large struct containing such a tuple can work, so this suggests to me some more intricate problem: ``` julia> mutable struct LargeStruct size::UInt32 data::NTuple{1024*1024*4,UInt32} end julia> a...

One additional worry I have with this is that this yet again doesn't handle "small" API changes relating to a single signature/method. For an already exported name, it's impossible to...

Should this actually be guaranteed, or is this a case of "that's what it happens to do right now"?

Which version are you seeing that on? On 1.11-alpha2 I see this:  Which makes sense, since the arguments are `Const` and thus are inaccessible. It's just weird that this...

That's good to know! The comment above that ("No definite size") indicates that this is primarily due to size concerns, but in practice, aren't most string constants that would be...

~Which version is this on? I can't reproduce this:~ Missed the bit about `Foo(1.0)` erroring, now I can reproduce it ```julia julia> struct Foo{T >: Int} x::T end julia> Foo(1.0)...