Can i use signal as object?

[ShestakovViktor]

Hello. I found interesting idea to use object wrapper with signal for better code readability, but i can't assume potential pitfalls of this approach. Maybe someone more expirienced with solidjs could say something about it.

import {
    Accessor,
    Setter,
    SignalOptions,
    createSignal as solidjsCreateSignal,
} from "solid-js";

type Signal<T> = {
    get: Accessor<T>;
    set: Setter<T>;
};

function createSignal<T>(
    value: T,
    options?: SignalOptions<T>
): Signal<T> {
    const [get, set] = solidjsCreateSignal(value, options);
    return {get, set};
}

const str = createSignal("");
str.set("Hello world");
str.get();

[AFatNiBBa]

The only pitfall I can think of your code is that the original createSignal() has multiple overloads, while your's hasn't.
I needed something similiar and I ended up creating a conversion function

import { Signal, createSignal } from "solid-js";

function toObject<T>([ get, set ]: Signal<T>) {
  return {
    get value() { return get(); },
    set value(v) { set(() => v); }
  };
}

//                   ↓ The other overload works too!
const obj = toObject(createSignal<number>());

(I wanted both readability and not having to worry about accidentally passing a function to the setter.)

Warning

If you, like me, end up liking the property approach you have to keep in mind that

const [ get, set ] = createSignal(0);
set(x => x + 1);

Is not the same as doing

const obj = toObject(createSignal(0));
obj.value++;

But rather

const obj = toObject(createSignal(0));
obj.value = untrack(() => obj.value) + 1;