Shane F. Carr

My OP was one suggestion, to establish the convention of `{ mantissa, scale }` to represent decimal numbers across APIs without adding a separate BigDecimal type. Intl was an example...

IMO, "is not viable" is too strong a statement at this stage, because we have not fully agreed on the goals. I would argue that representing repeated digits may not...

I would like to resolve the name bikeshed under the assumption that these functions are useful, which I believe they are, even if we aren't using them in the lookup...

Discuss with: - @sffc - @younies

```rust impl ZeroTrieSimpleAscii { pub const fn as_ref(&self) -> &ZeroTrieSimpleAscii } impl &ZeroTrieSimpleAscii { pub fn borrowed_store(self) -> ZeroTrieSimpleAscii; } impl AsRef for ZeroTrieSimpleAscii { fn as_ref(&self) => &ZeroTrieSimpleAscii {}...

FYI, this is one of the features of `"globwalk"` that isn't in `"glob"`: https://github.com/gilnaa/globwalk#why-not-glob

Not breaking the web is where the `"use stricter";` suggestion came from.

If you are able to publish your TypeScript library, I would be happy to recommend it as an alternative to this library. The ecosystem has changed a lot since this...

ryanaltair's solution looks like it should work, but I agree that it is not very elegant. One issue in ryanaltair's code: you'll need to increment `serialNum` to prevent two uploads...

Did you run `npm install` first?