Consider adding the ability to return an accessor in a function

If you want to return a getter and setter in a function, you have to wrap it in an object property. This can limit some abilities to implement more reactivity in ECMAScript. For example:

function logger(value){
    return {
        get value(){
            console.log('Value accessed!');
            return value;
        },
        set value(newVal){
            console.log(`Value changed to ${newVal}!`);
            value = newVal;
            return true;
        }
    }
}
let count = logger(0);
count.value++; //logs Value changed to 1!

is much less convenient and ergonomic than:

function logger(value){
    return accessor {
        get(){
            console.log('Value accessed!');
            return true;
        }
        set(newVal){
            console.log(`Value changed to ${newVal}!`);
            value = newVal;
            return true;
        }
    }
}
let count = logger(0);
count++; //logs Value changed to 1!

Returning accessors would allow for much simpler state management and reactivity in ECMAScript without any extra libraries or build steps. Some examples of where this could be used include:

Svelte 5's $state rune, in which a value is passed, and when set, triggers a state change in the DOM. (Svelte is a compiled language, but this would simplify functionality)
React's useState hook, in which a value is passed, and returns a getter and setter.
Vue's ref function, which declares a reactive state and returns an object with a value getter and setter.
A much simpler implementation of the Signals proposal, in which a value is passed, and returns a get function and set function.

tc39 / proposal-grouped-and-auto-accessors

Consider adding the ability to return an accessor in a function #16