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

Standard library status #567

Open
davesnx opened this issue May 11, 2023 · 3 comments
Open

Standard library status #567

davesnx opened this issue May 11, 2023 · 3 comments
Labels

Comments

@davesnx
Copy link
Member

davesnx commented May 11, 2023

The current Js and Belt are compatible with the ones shipped with rescript and those contain a few issues from the past 1 2 and a few issues from the present 1 2 (Those aren't necessary issues directly, but to showcase that most people spend time re-working the stdlib).

Without getting myself into a lot of troubles, we could work-out a bit the status of those modules considering:

  • Records are represented as JavaScript Objects.
  • Exceptions won't have the shape and we might be able to solve compatibility with JavaScript errors.
  • Pipe-first plays really well with labelled arguments while pipe-last plays very well without labelled arguments (and we have some examples of that: https://github.com/darklang/tablecloth-rescript)
  • We might want to cross-compile (or virtualise) them.
  • First versions of Melange will remain compatible but eventually we can forge it and evolve them freely.

Opening this issue to gather information/opinions on what's a good idea and what's a bad idea.

@anmonteiro
Copy link
Member

I'm open to ideas and contributions on this. However:

  • let's discuss each separate small change in isolation -- this is the stdlib after all and we need to be really mindful about changing it
  • expect some bikeshedding, and some ideas that won't be able to make it in

@davesnx
Copy link
Member Author

davesnx commented May 16, 2023

Totally, this issue is to discuss the bikeshedding and how to move forward. I'm currently doing a lot of work on this but happy to adapt/change anything.

I personally don't have much opinion about those topics, so anyone is more appropriate than me to drive this.

@texastoland
Copy link

Re. #731

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

No branches or pull requests

3 participants