Compiler panics when associated constant is initialized via const eval function

[ironcev]

The below example will panic with:

thread 'main' panicked at sway-core/src/semantic_analysis/type_check_analysis.rs:64:44:
called `Option::unwrap()` on a `None` value

library;

struct S {}

fn eval_s_c(val: u8) -> u8 {
    val
}

impl S {
    const S_C: u8 = eval_s_c(111);
}

Initializing a module constant works fine:

library;

fn eval_s_c(val: u8) -> u8 {
    val
}

const S_C: u8 = eval_s_c(111);