wasmerio/wasmer · error

no v128 type in Wasm C API yet!

Error message

no v128 type in Wasm C API yet!

What it means

Error "no v128 type in Wasm C API yet!" thrown in wasmerio/wasmer.

Source

Thrown at lib/c-api/src/wasm_c_api/types/value.rs:25

#[repr(u8)]
pub enum wasm_valkind_enum {
    WASM_I32 = 0,
    WASM_I64 = 1,
    WASM_F32 = 2,
    WASM_F64 = 3,
    WASM_EXTERNREF = 128,
    WASM_FUNCREF = 129,
    WASM_EXNREF = 130,
}

impl From<Type> for wasm_valkind_enum {
    fn from(other: Type) -> Self {
        match other {
            Type::I32 => Self::WASM_I32,
            Type::I64 => Self::WASM_I64,
            Type::F32 => Self::WASM_F32,
            Type::F64 => Self::WASM_F64,
            Type::V128 => todo!("no v128 type in Wasm C API yet!"),
            Type::ExternRef => Self::WASM_EXTERNREF,
            Type::FuncRef => Self::WASM_FUNCREF,
            Type::ExceptionRef => Self::WASM_EXNREF,
        }
    }
}

impl From<wasm_valkind_enum> for Type {
    fn from(other: wasm_valkind_enum) -> Self {
        use wasm_valkind_enum::*;
        match other {
            WASM_I32 => Type::I32,
            WASM_I64 => Type::I64,
            WASM_F32 => Type::F32,
            WASM_F64 => Type::F64,
            WASM_EXTERNREF => Type::ExternRef,
            WASM_FUNCREF => Type::FuncRef,
            WASM_EXNREF => Type::ExternRef,

View on GitHub (pinned to 8c4b9ee9d3)

When it happens

Trigger: Thrown at lib/c-api/src/wasm_c_api/types/value.rs:25 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of wasmerio/wasmer@8c4b9ee9d3 (2026-09-01). Data as JSON: /api/errors/ba72f0c4ece1f04f. Report an issue: GitHub.