Merge branch 'master' into playgroud-output-result-rebase-aspeddro

Author: aspeddro

.babelrc

@@ -0,0 +1,2 @@
+*.res linguist-language=ReScript
+*.resi linguist-language=ReScript

.gitattributes

@@ -15,8 +15,8 @@ _tempFile.cmj
 _tempFile.cmt
 
 # these docs are checked in, but we consider them frozen.
-pages/docs/manual/v8.0.0/
-pages/docs/manual/v9.0.0/
+# pages/docs/manual/v8.0.0/
+# pages/docs/manual/v9.0.0/
 
 .bsb.lock
 .merlin
@@ -26,3 +26,4 @@ lib/
 .vercel
 
 src/**/*.mjs
+scripts/**/*.mjs

.gitignore

@@ -30,17 +30,17 @@ If you need inspiration on what to work on, you can check out issues tagged with
 
 We really appreciate all input from users, community members and potential contributors. Please make sure to consider the other person's opinion and don't assume any common knowledge.
 
-**Most importantly: Keep it professional and be nice to each other**
+**Most importantly: Keep it professional and be nice to eachother**
 
-There might be situations where others don't understand a proposed feature or have different opinions on certain writing styles. That's fine, discussions are always welcome! Communicate in clear actionables, make your plans clear and always stick to the original topic.
+There might be situations where others don't understand a proposed feature or have different opinions on certain writing styles. That's fine, discussions are always welcome! Communicate in clear actionables, make your plans clear and always to stick to the original topic.
 
 If other contributors disagree with certain proposals and don't change their mind after longer discussions, please don't get discouraged when an issue gets closed / postponed. Everyone tries their best to make the platform better, and to look at it in another perspective: Closed issues are also a highly valuable resource for others to understand technical decisions later on.
 
 ### Communicate your Time Commitment
 
 Open Source development can be a challenge to coordinate, so please make sure to block enough time to work on your tasks and show commitment when taking on some work. Let other contributors know if your time schedule changes significantly, and also let others know if you can't finish a task.
 
-We value your voluntary work, and of course it's fine to step back from a ticket for any reason (we can also help you if you are getting stuck). Please talk to us in any case, otherwise we might re-assign the ticket to other contributors.
+We value your voluntary work, and of course it's fine to step back from a ticket for any reasons (we can also help you if you are getting stuck). Please talk to us in any case, otherwise we might re-assign the ticket to other contributors.
 
 ### Communication Channels
 
@@ -66,7 +66,7 @@ Always check if there are any designs for certain UI components and think about
 ### Technical Writing (Documentation)
 
 - Think and write in a JS friendly mindset when explaining concepts / showing examples.
-- No `foo` examples if somewhat possible. Try to establish practical context in your showcase examples.
+- No `foo` examples if somewhat possible. Try to establish practical context in your show case examples.
 - No references to `OCaml`. ReScript is its own language, and we don't rely on external resources of our host language.
 - If possible, no references to `Reason` examples / external resources. Our goal is to migrate everything to ReScript syntax.
 

CONTRIBUTING.md

@@ -61,7 +61,7 @@ There's no dedicated name for the syntax anymore. It's simply called the ReScrip
 
 **Will there be a migration script to gradually convert our code to the new syntax?**
 
-Yes. See our [migration page](/docs/manual/latest/migrate-from-bucklescript-reason). You can mix and match old and new code for a smoother transition.
+Yes. See our [migration page](/docs/manual/v10.0.0/migrate-from-bucklescript-reason). You can mix and match old and new code for a smoother transition.
 
 **Will BuckleScript (now ReScript) break my existing code?**
 

_blogposts/2020-08-10-bucklescript-is-rebranding.mdx

@@ -86,7 +86,7 @@ There are two ways of removing staled artifacts, the second one is introduced in
 
 - Based on live analysis and prebuilt-in knowledge
 
-We scan `lib/bs` directory and check some dangling cm{i,t,j,ti} files, if it does not exist in
+We scan `lib/bs` directory and check some dangling `cm{i,t,j,ti}` files, if it does not exist in
 the current build set, it is considered stale artifacts. If it is `cmt` file, it would trigger some hooks of `genType`, notably -cmt-rm.
 
 - Based on previous build logs

_blogposts/2020-09-25-release-8-3-2.mdx

@@ -16,7 +16,7 @@ ReScript is a robustly typed language that compiles to efficient and human-reada
 
 Use `npm` to install the newest [9.0.1 release](https://www.npmjs.com/package/bs-platform/v/9.0.1) with the following command:
 
-```
+```sh
 npm install bs-platform@9.0.1
 ```
 

_blogposts/2021-02-09-release-9-0.mdx

@@ -0,0 +1,150 @@
+---
+author: rescript-team
+date: "2023-09-18"
+title: Uncurried Mode
+badge: roadmap
+description: |
+  A tour of new capabilities coming to ReScript v11
+---
+
+> This is the fourth post covering new capabilities that'll ship in ReScript v11. You can check out the first post on [Better Interop with Customizable Variants](/blog/improving-interop), the second post on [Enhanced Ergonomics for Record Types](/blog/enhanced-ergonomics-for-record-types) and the third post on [First-class Dynamic Import Support](/blog/first-class-dynamic-import-support).
+
+## Introduction
+
+ReScript is a language that strives to keep its users free from experiencing runtime errors. Usually, when a program compiles, it will already do what the user described.
+But there is still a concept in the language that makes it easy to let some errors slip through. Currying! 
+
+Because of currying, partial application of functions is possible. That feature is always advertised as something really powerful. For instance, 
+
+```rescript
+let add = (a, b) => a + b
+let addFive = add(5)
+```
+
+is shorter than having to write all remaining parameters again 
+
+```rescript
+let add = (a, b) => a + b
+let addFive = (b) => add(5, b)
+```
+
+This comes at a price though. Here are some examples to show the drawbacks of currying: 
+
+* Errors because of changed function signatures have their impact at the use site. Consider this example, where the signature of the onChange function is extended with
+a labeled argument 
+  ```diff
+    @react.component
+  -  let make = (~onChange: string => option<unit => unit>) => {
+  +  let make = (~onChange: (~a: int, string) => option<unit => unit>) => {
+      React.useEffect(() => {
+        // As partial application is allowed, there is no error here.
+        let cleanup = onChange("change") 
+        
+        // Here it errors with "This call is missing an argument of type (~a: int)"
+        cleanup 
+      })
+    }
+  ```
+* If you wanted explicitly uncurry a function, you needed to annotate it with the uncurried dot. 
+  ```rescript
+  (. param) => ()
+  ```
+* As ReScript could not fully statically analyze when to automatically uncurry a function over multiple files, it led to unnecessary `Curry.` calls in the emitted JavaScript code. 
+* In the standard library (`Belt`), there are both curried and uncurried versions of the same function so you were required to think for yourself when to use the uncurried version and when only the curried one will work.
+* In combination with `ignore` / `let _ = ...`, curried can lead to unexpected behavior at runtime after adding a parameter to a function, because you are accidentally ignoring the result of a partial evaluation so that the function is not called at all.
+  1. Have a look at this simple function. It is assigned to `_` because we ignore the resulting `string` value. 
+    ```res
+    let myCurriedFn = (~first) => first
+    let _ = myCurriedFn(~first="Hello!")
+    //  ^ string
+    ```
+  2. Now the function got a second parameter `~second`. Here, the resulting value is a function, which means it is not fully applied and thus never executed.
+    ```res
+    let myCurriedFn = (~first, ~second) => first ++ " " ++ second
+    let _ = myCurriedFn(~first="Hello!")
+    //  ^ (~second: string) => string
+    ```
+  3. One way to prevent such errors is to annotate the underscore with the function's return type:
+    ```res
+    let _: string = myCurriedFn(~first="Hello!")
+    ```
+  4. However, the same issue arises when using the built-in ignore function, which cannot be annotated:
+    ```res
+    myCurriedFn(~first="Hello!")->ignore
+    ```
+
+Those are all only some small paper cuts, but all of them are intricacies that make the language harder to learn. 
+
+## Uncurried mode
+
+Starting with ReScript 11, your code will be compiled in uncurried mode. Yes, there is still a way to turn it off ([see below](#how-to-switch-back-to-curried-mode)), but we have decided to already default to this behavior to make it easier for newcomers.
+In uncurried mode, the introductory example yields an error:
+
+```rescript
+let add = (a, b) => a + b
+let addFive = add(5) // <-- Error:
+// This uncurried function has type (. int, int) => int
+// It is applied with 1 arguments but it requires 2.
+```
+
+to fix it, you have two options:
+
+1. state the remaining parameters explicitly 
+  ```rescript
+  let add = (a, b) => a + b
+  let addFive = (b) => add(5, b)
+  ```
+2. or use the new explicit syntax for partial application 
+  ```rescript
+  let add = (a, b) => a + b
+  let addFive = add(5, ...)
+  ```
+
+The former approach helps library authors support both ReScript 11 and earlier versions.
+
+### No final unit anymore
+
+We are happy to announce that with uncurried mode the "final unit" pattern is not necessary anymore, while you still can use optional or default parameters.
+
+```res
+// old 
+let myFun = (~name=?, ())
+
+// new
+let myFun = (~name=?)
+```
+
+### More wins
+
+Furthermore, function calls in uncurried mode are now guaranteed to get compiled as simple JavaScript function calls, which is quite nice for readability of the generated code. 
+It may also give you some (negligible) performance gains. 
+
+### How to switch back to curried mode
+
+While we strongly encourage all users to switch to the new uncurried mode, it is still possible to opt out. Just add a
+
+```json
+{
+  "uncurried": false
+}
+```
+
+to your `bsconfig.json`, and your project will be compiled in curried mode again.
+
+If you have uncurried mode off and still want to try it on a per-file basis, you can turn it on via 
+
+```rescript
+@@uncurried
+```
+
+at the top of a `.res` file.
+
+## Conclusion
+
+Many thoughts have led to this decision, but we think this change is a great fit for a compile-to-JS language overall. If you are interested in the details, have a look at the corresponding [forum post](https://forum.rescript-lang.org/t/uncurried-by-default/) and its comments.
+
+We hope that this new way of writing ReScript will make it both easier for beginners and also more enjoyable for the seasoned developers.
+
+As always, we're eager to hear about your experiences with our new features. Feel free to share your thoughts and feedback with us on our [issue tracker](https://github.com/rescript-lang/rescript-compiler/issues) or on the [forum](https://forum.rescript-lang.org).
+
+Happy hacking!

_blogposts/2023-09-18-uncurried-mode.mdx

@@ -26,7 +26,7 @@ A detailed list of changes are listed as below:
 - #1658, fix typeof = "null" issue
 - #1656, bs.get/set/get_index/set_index respects bs.ignore
 - #1654, `bsb -init` fails if package or current dir has space (parent dir can have spaces)
-- #1678, bs.get{null;undefined}  in object type
+- #1678, `bs.get{null;undefined}`  in object type
 - #1692, fix invalid js syntax output
 - #1701, fix tailcall handling interaction with  exception handler
 - #1666, fix misue of GADT api

_blogposts/archive/2017-10-09-bucklescript-release-1-7-5.mdx

@@ -0,0 +1 @@
+Console.log("I am a dummy file")

compilers/dummy/Dummy.res

@@ -5,10 +5,12 @@
   "main": "index.js",
   "license": "MIT",
   "dependencies": {
+    "@rescript/core": "^0.6.0",
+    "rescript-1000": "npm:rescript@10.0.0",
+    "rescript-1010": "npm:rescript@10.1.0-rc.4",
+    "rescript-1100": "npm:rescript@11.0.0-rc.8",
     "rescript-820": "npm:bs-platform@8.2.0",
     "rescript-902": "npm:bs-platform@9.0.2",
-    "rescript-912": "npm:rescript@9.1.2",
-    "rescript-1000": "npm:rescript@10.0.0",
-    "rescript-1010": "npm:rescript@10.1.0-rc.4"
+    "rescript-912": "npm:rescript@9.1.2"
   }
 }

compilers/package-lock.json

@@ -0,0 +1,13 @@
+{
+  "name": "dummy",
+  "sources": {
+    "dir": "dummy",
+    "subdirs": true
+  },
+  "bs-dependencies": [
+    "@rescript/core"
+  ],
+  "bsc-flags": [
+    "-open RescriptCore"
+  ]
+}

compilers/package.json

@@ -2,8 +2,8 @@
   "Overview": [
     "introduction",
     "installation",
+    "migrate-to-v11",
     "editor-plugins",
-    "migrate-from-bucklescript-reason",
     "try"
   ],
   "Language Features": [
@@ -31,7 +31,6 @@
     "module",
     "import-export",
     "attribute",
-    "unboxed",
     "reserved-keywords"
   ],
   "Advanced Features": [