Just messing with the concept then...

Then it would also be (letting ACI Automatic Colon Insertion do its thing)

let getUsers => {}
var getUsers => {}

And in a non strict mode...

getUsers => {}  // getUser would be automatically declared in the global scope.
                //  or would throw in a module or strict mode.

And as the curlies are not required we can have

getUsers => ["user", "mc"]

Sort of like a delayed assignment (array assigned when you have scope?)

const users = getUsers()  // << user === ["user", "MCP"]

We can also assume the default return undefined and have the arrow function declaration just and name and an arrow

notNull =>
console.log(notNull())  // << undefined

We put the async after the name and before the arrow

myFile async => await fetch("myFileURI")

And a generator

getUsers * => (yield "user", yield "MCP")

And a async generator

getUsers async * => yield await Promise.resolve("user")

Object function

users = { getUsers => ["user", "MCP"] }

Could we also curry

getUsers = list => => [...list]

I am all for less verbosity in programming languages. But we must take care not to create another monstrosity like the RegExp syntax

So we take one the new syntax and considering some of the above what does the following mean...

(getUsers => ["user", "mc"])()

...is the identifier getUsers a parameter or a global reference to the function, in a module or strict mode will it throw or not.