You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this would be more readable if you added a CreateMessageFormatNumberFunction abstract operation, instead of having the _numberSteps_ followed by CreateBuiltinFunction.
Let F be a new built-in function object as defined in Number Format Functions (15.5.2).
My main reason for this approach was that this way the :number and :string definitions can be left without the boilerplate code that's now here. But my opinions on this are not at all strong.
This has me equally stumped. On the one hand I agree with @dminor that an AO would be much more readable and less arcane than this.
On the other, I understand the connection to the other similar parts of the spec. I still lean towards AOs over dynamically creating ES builtin functions because my understanding of the MF2 builtin registry functions is that they'd not be actually dynamic and therefore we'll be fine by using an AO here.
The text was updated successfully, but these errors were encountered:
From #39 (comment):
@dminor:
@eemeli:
@ryzokuken:
The text was updated successfully, but these errors were encountered: