@SunsetTechuila feel free to merge when ready

Without any parameters, mem is identical to onetime but slower.

With parameters you're suggesting to extract 60% of the function's utility, placing the async getters outside the memoization.

At any rate it would be weird to have such a specific assertion that is essentially console.assert(arguments[0] === arguments[1], "error message"). At that point why have a memoized helper at all? a === b is not a useful memoization.

placing the async getters outside the memoization

We need two arguments for memoization: user (returned by sync getLoggedInUser) and token (returned by async getToken). assertCurrentUser is called by v4uncached and v3uncached. Both of these functions already call getToken.

@nntld thank you

Ok? And what expensive operation do you memoize exactly after taking those two out?

what expensive operation

I agree that switching from onetime to mem won't noticeably improve efficiency:

it's not a big deal

It will, however, marginally improve it for free

Taking those values out makes sense, memoizing the assertion afterwards does not.

It's either onetime to wrap the entire logic in a useful helper or no memoization at all.