Paul Draper

> But by this, the old module still never unloaded, it cause memory leak. > only remove from module list There is no module list, per se.

All of these concerns exist for static imports as well; it should really be a different proposal and include suggestions for those.

This suggestion 💯. I've found it difficult to adopt `using` for two reasons: 1. Non-disposable code requires awkward wrappers. ```ts // existing code function client() { return { // ......

> Irrelevant, the CORS spec says that multiple Access-Control-Allow-Origin headers is illegal > Rather, the header, according to the spec, may contain an origin list or null. No, the _Origin_...

#5811 is a interesting idea. Also, ambitious. But regardless of the status of #5811, both `RequestHeader` and `ResponseHeader` should be using the same header API. Today, `RequestHeader` uses `Headers`, and...

On that note, an ugly -- but technically correct -- workaround is to use different cases. ``` scala Unauthorized(msg).withHeaders( "WWW-Authenticate" -> "Basic test", "www-Authenticate" -> "Token test", "wWw-AuThEnTiCaTe" -> "Other...

> I'm sorry but this has already been discussed a lot and the best trade-off we've come up with is to keep objects multliline if they have a newline inside....

You can use https://github.com/resolritter/prettier-plugin-compactify though that project isn't active. (And you can only have one of these "preprocess" plugins per language....I already use prettier-plugin-organize-imports.)

The current behavior is...odd to say the least. **.bazelignore** ```txt dir ``` **BUILD.bazel** ```py filegroup( name = "example1", srcs = ["dir/example.txt"] ) filegroup( name = "example2", srcs = glob(["dir/example.txt"]) )...

As described in Java doc, this is meant to only avoid interpreting BUILD files, and nothing else. ``` /** * The file .bazelignore can be used to specify directories to...