龙腾道 comments

Results 56 comments of


                                            龙腾道

trafficstars

Add information which is possible to cause conflict to doc

I think this is like the occupancy of global variables in daily programming, which cannot be ignored because of the low probability.

Is empty tuple / record falsy?

If empty is falsy, what value does this additional difference generate? I can't image when any code I seen try to check specially whether there is keys in an options...

What about sets?

```js const queue = #[ 'encodeURIComponent', 'encodeURIComponent', 'base64' ]; for ( const task of queue ) { input = process(input, task); } queue===#[ 'encodeURIComponent', 'base64' ]; // false const valueSet...

[Feature] Comment Preservation Proposal

(I have a stringify solution discussion , which includes comment:) > Comment > ------- > > Another pain is comment. Obviously we don't want a configuration file that contains comments...

Why $::util:toSet() equals to toSet($) but not toSet.cal($) in README "Example of using constructors or namespace object as extensions"?

@m93a It's still in README: https://github.com/tc39/proposal-extensions/blame/master/README.md#L64

Type annotations for default export

Maybe `export const default :Type = value;` `export type default = Type;` `export interface default {}` could bring us more uniformity, avoid to introduce a new set of grammars just...