Asked a few people and summarized into this
Make it compile to native
@chenglou @bobzhang Is the plan to use bsb-native to compile "Universal Belt"? I'm asking because if that's the case we could use the BSB_BACKEND flag, and it would be a great "eat your own food" opportunity, to evaluate the experience of writing cross-platform code with BuckleScript.
as a standalone js library
Will this package just include Belt? Or the stdlib too? In https://github.com/BuckleScript/bucklescript/pull/2171 I started some preliminary steps to publish the stdlib as a standalone package (change templates, guarantee that both bs-platform and this new package stay in sync) that I could maybe revive for this.
Yeah it would. Only need to standardize on a single env var name.
Will this package just include Belt?
Let's keep it just for Set/Map and their variations for now.
Ok I think in terms of native compilation, I'm just gonna copy the sources into my project & fiddle with them until they work
Ping here if you need any help understanding the conditional compilation: https://bucklescript.github.io/docs/en/conditional-compilation.html
Option done! Thanks @arnarthor!
@jaredly we will support it on native. The worst thing is that we just keep the interface file and provide an alternative implementation. But let's wait for a while to allow some stability
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Most helpful comment
Option done! Thanks @arnarthor!