A wee convenience for signals?

[pragdave]

What do y'all think of adding .get as a synonym for this[0] and .set as a synonym for this[1] in the return value of createSignal?

For example, I currently write:

  const psw = createSignal(0)

  dispatcher.register(ET.tPswUpdated, (ev: Event.EmulatorEvent) => {
    psw[1](ev.psw)
  })

but it would be (marginally) nicer to write

  const psw = createSignal(0)
  . . .
    psw.set(ev.psw)

[atk]

Using a tuple is the smallest convenient way to return two items at once. You can write your own abstraction over createSignal:

const createSignalObj = (...args) => {
  const [get, set] = createSignal(...args);
  return { get, set };
};

[msteen]

If you want the latter syntax, this is already done internally in the store part of Solid:

solid/packages/solid/store/src/store.ts

Lines 122 to 136 in 17763fa

	function createDataNode(value?: any, equals?: boolean) {
	const [s, set] = createSignal<any>(
	value,
	equals
	? {
	internal: true
	}
	: {
	equals: false,
	internal: true
	}
	);
	(s as Accessor<any> & { $: (v: any) => void }).$ = set;
	return s as Accessor<any> & { $: (v: any) => void };
	}

So you could do something like this (to make your marginally nicer variant work):

import { Accessor, createSignal, Setter,  } from 'solid-js';
import { SignalOptions } from 'solid-js/types/reactive/signal';

function createSignalCombined<T>(value: T, options: SignalOptions<T>) {
    const [get, set] = createSignal(value, options);
    (get as Accessor<any> & { set: Setter<T> }).set = set;
    return get as Accessor<any> & { set: Setter<T> };
}