Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow nameCache to be a concurrenthashmap #1247

Open
masx200 opened this issue Aug 23, 2022 · 3 comments
Open

allow nameCache to be a concurrenthashmap #1247

masx200 opened this issue Aug 23, 2022 · 3 comments

Comments

@masx200
Copy link

masx200 commented Aug 23, 2022

Bug report or Feature request?

feature request
Version (complete output of terser -V or specific git commit)
5.15.0
Complete CLI command or minify() options used

minify() api
terser input

terser output or error

Expected result

https://github.com/mmomtchev/SharedMap

https://www.npmjs.com/package/terser-webpack-plugin

https://www.npmjs.com/package/rollup-plugin-terser

Today's popular bundler uses terser, and you can use worker to compress many output files in parallel, but when using mangle.properties, you need to read and write simultaneously.

allow nameCache to be a concurrenthashmap

@masx200
Copy link
Author

masx200 commented Aug 23, 2022

@masx200
Copy link
Author

masx200 commented Aug 23, 2022

@masx200
Copy link
Author

masx200 commented Aug 23, 2022

evanw/esbuild#2493 (comment)

https://github.com/orcaman/concurrent-map

The current concurrenthashmap in JavaScript may not be mature, but there is already a mature concurrenthashmap in golang, which is a concurrency security version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant