Lazy once_cell causes stack overflow - rust

Question

The code:
use once_cell::sync::Lazy;
fn main() {
const TEST: Lazy<[[u64; 64]; 512]> = Lazy::new(|| unimplemented!());
TEST[0];
}
Results in the output:
thread 'main' has overflowed its stack
error: process didn't exit successfully: `target\debug\chess_ai.exe` (exit code: 0xc00000fd, STATUS_STACK_OVERFLOW)
Weirdly enough only on windows. On Linux (WSL Debian GNU/Linux 9), the output is the expected:
Finished dev [unoptimized + debuginfo] target(s) in 23.38s
Running `target/debug/chess_ai`
thread 'main' panicked at 'not implemented', src/main.rs:4:56
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Am I being a banana, lol? I don't understand at all what's going on here. This is also a pretty hard roadblock for me right now, so I really appreciate responses!
Playground version works as expected.
Versions
once_cell: "1.12.0"
rustc (both windows and Linux): "1.61.0"

Answer 1

So after some testing it seems like the stack is just not big enough to contain my variable, since this, plain, piece of code also results in a stackoverflow:
fn main() {
let test: [[u64; 64]; 3000] = [[0; 64]; 3000];
test[0];
}
Given that the const in the question is not really "generated"/"created" (lazy initialization) at compile time, it happens inside a stack-frame and most likely causes the stackoverflow.
Moving the data to the heap fixes the issue:
use once_cell::sync::Lazy;
fn main() {
static TEST: Lazy<Box<[[u64; 64]; 512]>> = Lazy::new(|| unimplemented!());
TEST[0];
}
Seems like windows and Linux versions have different stack sizes, or the code is optimized differently.