Eemeli Aro

Closing as presumably answered.

That's a fair concern. A method for discovering unresolved aliases should be provided, and a parsing option to include errors for them.

Pondering now whether something actually needs to be added, as this works, and provides an opportunity to take whatever locally appropriate action when encountering an unresolvable alias. ```js import {...

Closing, as the approach in the preceding comment should fulfill the user need, as seen e.g. [here](https://github.com/msivasubramaniaan/yaml-language-server/blob/4a5c6ca04f5700ac567007d0fa37a1482ad87ca0/src/languageservice/services/validation/unused-anchors.ts#L31-L35).

This is pretty much the same as https://github.com/eemeli/yaml/discussions/490. As I mention there: > YAML does not specify how comments are attached, and as you see here, there isn't always just...

I would reiterate that you're welcome to suggest changes in the logic for comment attachment, but you'll probably need to submit a PR yourself.

Closing due to lack of interest.

BigInt support for Intl.NumberFormat was added in #236. I can't find any notes or mentions around then or since about BigInt in Intl.PluralRules, but I do vaguely recall this having...

For context, the MF2 spec currently includes this for its `:number` [options](https://github.com/unicode-org/message-format-wg/blob/main/spec/registry.md#options-1): > The following values for the option `style` are _not_ part of the default registry. Implementations SHOULD avoid...

PR #988 ended up only removing `style=percent`. We do have `:unit unit=percent`, but that doesn't scale the input, so I'm reopening this to mark that we still need a solution...