The only things I've seen in the JS community with regards to nested namespaces is capitalizing them. Such as in https://www.typescriptlang.org/docs/handbook/namespaces.html

namespace Shapes {
  export namespace Polygons {
    export class Triangle {}
    export class Square {}
  }
}

To me, Temporal.now is more like globalThis.parseInt , not React.PropTypes :)

legendecas: that's not a break completion though

Just to share some results from searching in the community. Looking through all of the library/framework APIs which are documented by TypeScript in the DefinitelyTyped repository. You can find lots of examples of nested namespaces using both lowercase/capitalized naming: https://sourcegraph.com/search?q=context:global+repo:DefinitelyTyped/DefinitelyTyped+namespace+%5Ba-zA-Z0-9%5D%2B%5C.%5Ba-zA-Z0-9%5D%2B.*%5C%7B%24&patternType=regexp

500+ results for Upper.Upper, 142 for Upper.lower

Do you have case-sensitive enabled, I'm getting 194 for Upper.Upper?

the names are from https://tc39.es/process-document/

Referring to stage 0 stuff as "proposal" is already the norm in the community https://twitter.com/search?q=tc39%20stage%200%20proposal&src=typed_query

what is a temp check?

Having several "yes" choices but only one "no" choice is too biased.

And it leads to ambiguities like what we just encountered.

Actually it's hard to say the platforms implementation TextEncoder/TextDecoder are all same and correct :)

There are plenty of JS features I've needed to create my own versions of, but that doesn't detract from the usefulness of having a version of them in the language

many time , u need buffer.tobase64Buffer() ...

but we can choose one, I'd prefer urlsafe

yeah I guess it should not allowed , but it's a little weird that module m{}; import x from m works but let m = module m{}; import x from m not.

I would really like to see some syntax like what exists in Rust to import from the enclosing "parent" module

#[cfg(test)]
mod tests {
  use super::*;
}

@devsnek do we really need nested import? consider we have the url syntax which already have nested path for module...

i'd prefer a null object over a map

ljharb: can't do an iterable, only finite structures

Stage - 0 is an idea
Stage - 1 defining the problem
Stage - 2 defining the solution

^ sounds good?

Name a javascript developer that doesnt use console.log :P

I'm also having a hard time coming up with an example where it would even be observable.

well that was an unexpected outcome