When binding functions that return pointers (either raw or smart pointers) to a type or accept them as a argument, those values can be nullptr on the c++ side. We think that the TS bindings generated through --emit-tsd should respect this. For instance:

struct Foo {};
Foo* foo1() { return new Foo(); };
void foo2(Foo* foo) {};

EMSCRIPTEN_BINDINGS(Bar)
{
	em::class_<Foo>("Foo");
	em::function("foo1", &foo1, em::allow_raw_pointers());
	em::function("foo2", &foo2, em::allow_raw_pointers());
}

will emit the following TS bindings:

export interface Foo {
  delete(): void;
}
interface EmbindModule {
  Foo: {};
  foo1(): Foo;
  foo2(_0: Foo): void;
}

however I would have expected

  foo1(): Foo | null;
  foo2(_0: Foo | null): void;

since C++'s nullptr is a valid input/output for foo1/2() and therefore the same counts for the JavaScript side.

Am I missing something?

Note that using std::optional<Foo> is not really an option because Foo is not necessarily a value type that can be copied around/easily wrapped into an optional.

Version of emscripten/emsdk:

emcc (Emscripten gcc/clang-like replacement + linker emulating GNU ld) 3.1.62 (34c1aa36052b1882058f22aa1916437ba0872690)
clang version 19.0.0git (https:/github.com/llvm/llvm-project c00ada070207979f092be9046a02fcfff8b9f9ce)
Target: wasm32-unknown-emscripten
Thread model: posix