{React.string(`Hello ${name}`)}
+ }
+}
+
+module ClassicModeExample = {
+ // "classic" mode will compile jsx to React.createElement calls
+ @@jsxConfig({version: 4, mode: "classic"})
+
+ @react.component
+ let make = (~name) => {
+ {React.string(`Hello ${name}`)}
+ }
+}
+
+module NoAttributeExample = {
+ // No need for `makeProps` anymore
+ type props = {name: string}
+
+ let make = (props: props) => {
+ {React.string(`Hello ${props.name}`)}
+ }
+}
+
+module ReactInterfaceExample: {
+ @react.component
+ let make: (~name: string, ~age: int=?) => React.element
+} = {
+ @react.component
+ let make = (~name, ~age=0) => {
+
+ {React.string(
+ `Hello ${name}, you are ${Belt.Int.toString(age)} years old.`,
+ )}
+
+ }
+}
+
+module PropTypeInjectionExample = {
+ // Let's assume we have a prop type that we wanna enforce
+ // as our labeled arguments
+ type someoneElsesProps = {isHuman: bool}
+
+ // Here we tell the `react.component` decorator what props to infer.
+ // Useful for e.g. NextJS usage, or to create components that should
+ // comply to certain library component interfaces
+ @react.component(: someoneElsesProps)
+ let make = (~isHuman) => {
+ let msg = switch isHuman {
+ | true => "hello human"
+ | false => "hello fellow computer"
+ }
+ {React.string(msg)}
+ }
+}
+
+module PropSpreadExample = {
+ // Note: This will require @rescript/react 0.11 or later
+ @@jsxConfig({version: 4, mode: "automatic"})
+
+ @react.component
+ let make = () => {
+ let props = {NoAttributeExample.name: "World"}
+
+
+
+```
+
+```js
+import * as React from "react";
+import * as JsxRuntime from "react/jsx-runtime";
+
+function Playground$AutomaticModeExample(props) {
+ return JsxRuntime.jsx("div", {
+ children: "Hello " + props.name + ""
+ });
+}
+
+var AutomaticModeExample = {
+ make: Playground$AutomaticModeExample
+};
+
+function Playground$ClassicModeExample(props) {
+ return React.createElement("div", undefined, "Hello " + props.name + "");
+}
+
+var ClassicModeExample = {
+ make: Playground$ClassicModeExample
+};
+
+function make(props) {
+ return JsxRuntime.jsx("div", {
+ children: "Hello " + props.name + ""
+ });
+}
+
+var NoAttributeExample = {
+ make: make
+};
+
+function Playground$ReactInterfaceExample(props) {
+ var age = props.age;
+ var age$1 = age !== undefined ? age : 0;
+ return JsxRuntime.jsx("div", {
+ children: "Hello " + props.name + ", you are " + String(age$1) + " years old."
+ });
+}
+
+var ReactInterfaceExample = {
+ make: Playground$ReactInterfaceExample
+};
+
+function Playground$PropTypeInjectionExample(props) {
+ var msg = props.isHuman ? "hello human" : "hello fellow computer";
+ return JsxRuntime.jsx("div", {
+ children: msg
+ });
+}
+
+var PropTypeInjectionExample = {
+ make: Playground$PropTypeInjectionExample
+};
+
+function Playground$PropSpreadExample(props) {
+ return JsxRuntime.jsx(make, {
+ name: "World"
+ });
+}
+
+var PropSpreadExample = {
+ make: Playground$PropSpreadExample
+};
+
+var root = JsxRuntime.jsxs("div", {
+ children: [
+ JsxRuntime.jsx(Playground$AutomaticModeExample, {
+ name: "Automatic"
+ }),
+ JsxRuntime.jsx(Playground$ClassicModeExample, {
+ name: "Classic"
+ }),
+ JsxRuntime.jsx(make, {
+ name: "NoAttribute"
+ }),
+ JsxRuntime.jsx(Playground$ReactInterfaceExample, {
+ name: "Interface"
+ }),
+ JsxRuntime.jsx(Playground$PropTypeInjectionExample, {
+ isHuman: true
+ }),
+ JsxRuntime.jsx(Playground$PropSpreadExample, {})
+ ]
+ });
+
+export {
+ AutomaticModeExample ,
+ ClassicModeExample ,
+ NoAttributeExample ,
+ ReactInterfaceExample ,
+ PropTypeInjectionExample ,
+ PropSpreadExample ,
+ root ,
+}
+```
+{text->React.string}
+}
+```
+
+Now let's dynamically import the `
+ {Preact.string("Hello " ++ name)}
+
+}
+```
+
+Read more in the [new documentation on the generic JSX transform](/docs/manual/latest/jsx#generic-jsx-transform-jsx-beyond-react-experimental).
+
+## Tagged template literals
+
+This release comes with support for [tagged templates](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals#tagged_templates).
+
+A tag function in JavaScript is a function that expects an array of strings and variadic parameters as input. Now it's possibe to bind to such functions with the new [`@taggedTemplate`](/syntax-lookup#taggedTemplate-decorator) decorator:
+
+
@@ -45,7 +44,7 @@ As you can see, the `id` module changed from an array into an JS object.
## Pattern match code generation with annotations
-BuckleScript aims to generate readable code.
+BuckleScript aims to generate readable code.
OCaml has a sophiscated pattern match compiler, it generates well optimized
code, however, for complex pattern matching, the constructor name is lost on
@@ -56,7 +55,7 @@ complex pattern match.
In this release, we made such information available to JS backend so that we
annotate the generated JS code with its names.
-Below is an image showing the diff in this release
+Below is an image showing the diff in this release
@@ -65,7 +64,7 @@ In the future, we will explore if we can produce such annotation in the runtime
## Code generation improvement in various places
We care about the generated code quality, and will always keep improving it
-regardless how good it is.
+regardless how good it is.
In this release, we improved the code generation in quite a lot of places
including lazy evaluation, if branches and pattern match.
diff --git a/_blogposts/archive/another-encoding.mdx b/_blogposts/archive/2019-10-16-another-encoding.mdx
similarity index 96%
rename from _blogposts/archive/another-encoding.mdx
rename to _blogposts/archive/2019-10-16-another-encoding.mdx
index f5cd2bb3e..900069c13 100644
--- a/_blogposts/archive/another-encoding.mdx
+++ b/_blogposts/archive/2019-10-16-another-encoding.mdx
@@ -1,8 +1,7 @@
---
author: hongbo
-date: "2019-10-16"
+date: "2019-10-16"
previewImg:
-category: compiler
title: Another way of encoding type identity for BuckleScript libraries without using big functor
description: |
---
@@ -81,7 +80,7 @@ Error: This expression has type Ins2.coll
but an expression was expected of type Ins1.coll
```
-There are some issues with such encoding:
+There are some issues with such encoding:
- From runtime point of view, `Ins1` is initialized during runtime, its
implementation is a *big closure*, which means even if you only use on
@@ -182,8 +181,8 @@ When we mix `a0` and `a1`, we will get a type error
File ..., line 71, characters 13-15:
Error: This expression has type (int, S1.identity) Coll.coll
but an expression was expected of type (int, S0.identity) Coll.coll
- Type S1.identity is not compatible with type S0.identity
-```
+ Type S1.identity is not compatible with type S0.identity
+```
As you read here, by using such encoding, the data structure is more
generalized from user point of view. The generated JS code is not in a big
diff --git a/_blogposts/archive/whats-new-in-7-pt1.mdx b/_blogposts/archive/2019-11-18-whats-new-in-7-pt1.mdx
similarity index 97%
rename from _blogposts/archive/whats-new-in-7-pt1.mdx
rename to _blogposts/archive/2019-11-18-whats-new-in-7-pt1.mdx
index 9485dcf14..b13ad7b60 100644
--- a/_blogposts/archive/whats-new-in-7-pt1.mdx
+++ b/_blogposts/archive/2019-11-18-whats-new-in-7-pt1.mdx
@@ -1,8 +1,7 @@
---
author: hongbo
-date: "2019-11-18"
+date: "2019-11-18"
previewImg:
-category: compiler
badge: testing
title: What's new in BuckleScript v7 (Part 1)
description: |
@@ -55,7 +54,7 @@ var obj = {
y: 2,
z: 2
};
-```
+```
This new change makes record much more useful and its interaction with
`private` type; unboxed option type will make interop with JS much nicer!
diff --git a/_blogposts/archive/whats-new-in-7-pt2.mdx b/_blogposts/archive/2019-11-28-whats-new-in-7-pt2.mdx
similarity index 94%
rename from _blogposts/archive/whats-new-in-7-pt2.mdx
rename to _blogposts/archive/2019-11-28-whats-new-in-7-pt2.mdx
index f5d17fa16..b4e8dae10 100644
--- a/_blogposts/archive/whats-new-in-7-pt2.mdx
+++ b/_blogposts/archive/2019-11-28-whats-new-in-7-pt2.mdx
@@ -1,8 +1,7 @@
---
author: hongbo
-date: "2019-11-28"
+date: "2019-11-28"
previewImg:
-category: compiler
badge: testing
title: What's new in BuckleScript v7 (Part 2)
description: |
@@ -44,7 +43,7 @@ function f4(param) {
}
```
-As you can see, you can manipulate js objects using Reason pattern match syntax, the generated
+As you can see, you can manipulate js objects using Reason pattern match syntax, the generated
code is highly efficient, more importantly, bindings to JS will be significantly simplifie.
Happy Hacking.
diff --git a/_blogposts/archive/bucklescript-release-7-0-2.mdx b/_blogposts/archive/2019-12-20-bucklescript-release-7-0-2.mdx
similarity index 97%
rename from _blogposts/archive/bucklescript-release-7-0-2.mdx
rename to _blogposts/archive/2019-12-20-bucklescript-release-7-0-2.mdx
index 7a5e5e11f..a5e280e15 100644
--- a/_blogposts/archive/bucklescript-release-7-0-2.mdx
+++ b/_blogposts/archive/2019-12-20-bucklescript-release-7-0-2.mdx
@@ -1,8 +1,7 @@
---
author: hongbo
-date: "2019-12-20"
+date: "2019-12-20"
previewImg:
-category: compiler
badge: release
title: Announcing BuckleScript 7.0.2-dev.1
description: |
@@ -48,7 +47,7 @@ the maximum value with less confusing error messages!
The exciting thing about this feature is that we will now have more ways of
expressing our programs in our typical type safe records and variants without
-sacrificing on runtime performance ("zero cost interop").
+sacrificing on runtime performance ("zero cost interop").
The best way to understand this feature is by looking at the following
examples:
@@ -115,14 +114,14 @@ to get a better idea of how the example data structure is defined.
```reason
[@unboxed]
-type t =
- | Any ('a) : t;
+type t =
+ | Any ('a) : t;
let array = [|Any(3), Any("a")|];
```
```ocaml
(* OCaml *)
-type t =
+type t =
| Any : 'a -> t
[@@unboxed]
diff --git a/_blogposts/archive/bucklescript-release-7-1-0.mdx b/_blogposts/archive/2020-02-04-bucklescript-release-7-1-0.mdx
similarity index 96%
rename from _blogposts/archive/bucklescript-release-7-1-0.mdx
rename to _blogposts/archive/2020-02-04-bucklescript-release-7-1-0.mdx
index f5d9478e8..eb34a129c 100644
--- a/_blogposts/archive/bucklescript-release-7-1-0.mdx
+++ b/_blogposts/archive/2020-02-04-bucklescript-release-7-1-0.mdx
@@ -1,8 +1,7 @@
---
author: hongbo
-date: "2020-02-04"
+date: "2020-02-04"
previewImg:
-category: compiler
tags:
- Release
title: Announcing BuckleScript 7.1.0
diff --git a/_blogposts/archive/union-types-in-bucklescript.mdx b/_blogposts/archive/2020-02-07-union-types-in-bucklescript.mdx
similarity index 82%
rename from _blogposts/archive/union-types-in-bucklescript.mdx
rename to _blogposts/archive/2020-02-07-union-types-in-bucklescript.mdx
index d8fd81a5a..defdf25df 100644
--- a/_blogposts/archive/union-types-in-bucklescript.mdx
+++ b/_blogposts/archive/2020-02-07-union-types-in-bucklescript.mdx
@@ -1,8 +1,7 @@
---
author: hongbo
-date: "2020-02-07"
+date: "2020-02-07"
previewImg:
-category: compiler
title: Union types in BuckleScript
description: |
In our our 7.1.0 release we introduced the new [@unboxed] feature for better
@@ -25,9 +24,9 @@ introduction of unboxed attributes in `7.1.0`, we can create such types as
follows:
```ocaml
-type t =
- | Any : 'a -> t
-[@@unboxed]
+type t =
+ | Any : 'a -> t
+[@@unboxed]
let a (v : a) = Any v
let b (v : b) = Any v
let c (v : c) = Any v
@@ -46,15 +45,15 @@ let c = (v: c) => Any(v);
> module system, we can achieve this:
```ocaml
-module A_b_c : sig
- type t
- val a : a -> t
- val b : b -> t
- val c : c -> t
-end= struct
-type t =
- | Any : 'a -> t
-[@@unboxed]
+module A_b_c : sig
+ type t
+ val a : a -> t
+ val b : b -> t
+ val c : c -> t
+end= struct
+type t =
+ | Any : 'a -> t
+[@@unboxed]
let a (v : a) = Any v
let b (v : b) = Any v
let c (v : c) = Any v
@@ -70,38 +69,38 @@ module A_b_c: {
} = {
[@unboxed]
type t =
- | Any('a): t;
+ | Any('a): t;
let a = (v: a) => Any(v);
let b = (v: b) => Any(v);
let c = (v: c) => Any(v);
};
```
-What happens when we need to know specifically whether we have a value of type `a`? This is a case by case issue; it depends on whether there are some intersections in the runtime encoding of `a`, `b` or `c`. For some primitive types, it is easy enough to use `Js.typeof` to tell the difference between, e.g, `number` and `string`.
+What happens when we need to know specifically whether we have a value of type `a`? This is a case by case issue; it depends on whether there are some intersections in the runtime encoding of `a`, `b` or `c`. For some primitive types, it is easy enough to use `Js.typeof` to tell the difference between, e.g, `number` and `string`.
Like [type guards in typescript](https://www.typescriptlang.org/docs/handbook/advanced-types.html#type-guards-and-differentiating-types), we have to trust the user knowledge to differentiate between union types. However, such user level knowledge is isolated in a single module so that we can reason about its correctness locally.
Let's have a simple example, `number_or_string` first:
```ocaml
-module Number_or_string : sig
- type t
- type case =
- | Number of float
+module Number_or_string : sig
+ type t
+ type case =
+ | Number of float
| String of string
- val number : float -> t
- val string : string -> t
- val classify : t -> case
-end = struct
- type t =
- | Any : 'a -> t
- [@@unboxed]
- type case =
- | Number of float
+ val number : float -> t
+ val string : string -> t
+ val classify : t -> case
+end = struct
+ type t =
+ | Any : 'a -> t
+ [@@unboxed]
+ type case =
+ | Number of float
| String of string
- let number (v : float) = Any v
- let string (v : string) = Any v
- let classify (Any v : t) : case =
+ let number (v : float) = Any v
+ let string (v : string) = Any v
+ let classify (Any v : t) : case =
if Js.typeof v = "number" then Number (Obj.magic v : float)
else String (Obj.magic v : string)
end
@@ -135,24 +134,24 @@ module Number_or_string: {
Note that here we use `Obj.magic` to do an unsafe type cast which relies on `Js.typeof`. In practice, people may use `instanceof`; the following is an imaginary example:
```ocaml
-module A_or_b : sig
- type t
- val a : a -> t
- val b : b -> t
- type case =
- | A of a
- | B of b
+module A_or_b : sig
+ type t
+ val a : a -> t
+ val b : b -> t
+ type case =
+ | A of a
+ | B of b
val classify : t -> case
end = struct
- type t =
+ type t =
| Any : 'a -> t
- [@@unboxed]
- type case =
- | A of a
- | B of b
- let a (v : a) = Any v
+ [@@unboxed]
+ type case =
+ | A of a
+ | B of b
+ let a (v : a) = Any v
let b = (v : b) = Any v
- let classify ( Any v : t) =
+ let classify ( Any v : t) =
if [%raw{|function (a) { return a instanceof globalThis.A}|}] v then A (Obj.magic v : a)
else B (Obj.magic b)
end
diff --git a/_blogposts/archive/loading-stdlib-in-memory.mdx b/_blogposts/archive/2020-02-20-loading-stdlib-in-memory.mdx
similarity index 93%
rename from _blogposts/archive/loading-stdlib-in-memory.mdx
rename to _blogposts/archive/2020-02-20-loading-stdlib-in-memory.mdx
index 18a06658f..458380c02 100644
--- a/_blogposts/archive/loading-stdlib-in-memory.mdx
+++ b/_blogposts/archive/2020-02-20-loading-stdlib-in-memory.mdx
@@ -1,12 +1,11 @@
---
author: hongbo
-date: "2020-02-20"
+date: "2020-02-20"
previewImg:
-category: compiler
title: Improving the Stdlib Loading mechanism
description: |
We want to give you some insights on how we will improve the way BuckleScript
- compiles and handles its stdlib modules.
+ compiles and handles its stdlib modules.
---
## Loading stdlib from memory
@@ -24,13 +23,13 @@ You can try it via `npm i bs-platform@7.2.0-dev.4`
When the compiler compiles a module `test.ml`, the module `Test` will import
some modules from stdlib. This is inevitable since even basic operators in
BuckleScript, for example `(+)`, are defined in the Pervasives module, which is
-part of the stdlib.
+part of the stdlib.
Traditionally, the compiler will consult `Pervasives.cmi`, which is a binary
artifact describing the interface of the Pervasives module and
`Pervasives.cmj`, which is a binary artifact describing the implementation of
the Pervasives module. `Pervasives.cm[ij]` and other modules in stdlib are
-shipped together with the compiler.
+shipped together with the compiler.
**This traditional mode has some consequences:**
@@ -52,7 +51,7 @@ requests](https://github.com/BuckleScript/bucklescript/issues/2772).
In this release, we solve the problem by embedding the binary artifacts into
-the compiler directly and loading it on demand.
+the compiler directly and loading it on demand.
To make this possible, we try to make the binary data platform agnostic and as
compact as possible to avoid size bloating. The entrance of loading cmi/cmj has
@@ -82,7 +81,7 @@ The compiler is just one relocatable file. This makes the separation between
the compiler and generated JS artifacts easier. The remaining work is mostly to
design a convention between compiler and stdlib version schemes.
-### Better compilation performance
+### Better compilation performance
A large set of files is not loaded from the file system but rather from memory
now!
@@ -90,7 +89,7 @@ now!
### Fast installation and reinstallation.
Depending on your network speed, the installation is reduced from 15
-seconds to 3 seconds. Reinstallation is almost a no-op now.
+seconds to 3 seconds. Reinstallation is almost a no-op now.
@@ -116,7 +115,7 @@ Here is the new layout:
|
|-- win32
| |-- bsb.exe
-| |-- bsc.exe
+| |-- bsc.exe
|
|---darwin
| |-- bsb.exe
diff --git a/_blogposts/archive/bucklescript-release-7-2.mdx b/_blogposts/archive/2020-03-12-bucklescript-release-7-2.mdx
similarity index 96%
rename from _blogposts/archive/bucklescript-release-7-2.mdx
rename to _blogposts/archive/2020-03-12-bucklescript-release-7-2.mdx
index 260bbc534..c5a3c4f4f 100644
--- a/_blogposts/archive/bucklescript-release-7-2.mdx
+++ b/_blogposts/archive/2020-03-12-bucklescript-release-7-2.mdx
@@ -2,14 +2,13 @@
author: hongbo
date: "2020-03-12"
previewImg:
-category: compiler
tags:
- Release
title: Announcing BuckleScript 7.2
description: |
This release will give us some small quality of life improvements for tool
builders, better performance, and a new let %private modifier for hiding
- module functionality.
+ module functionality.
---
## About the Release
@@ -35,7 +34,7 @@ installation time.
However, with this release the installation is so fast that we recommend
installing it locally instead - per project - instead, as there's no additional
-cost, and it provides better isolation.
+cost, and it provides better isolation.
You can use it with a nice tool called
[npx](https://www.npmjs.com/package/npx), for example, `npx bsb`.
@@ -55,7 +54,7 @@ In OCaml's module system, everything is public by default, the only way to hide
```reason
module A : { let b : int} = {
let a = 3 ;
- let b = 4 ;
+ let b = 4 ;
}
```
@@ -86,7 +85,7 @@ We responded to this, and after some hard work - but _without_ changing the unde
A micro-benchmark for comparison:
```
running on 7.1
-Int64.to_string: 367.788ms # super positive number
+Int64.to_string: 367.788ms # super positive number
Int64.to_string: 140.451ms # median number
Int64.to_string: 375.471ms # super negative number
diff --git a/_blogposts/archive/generalize-uncurry.mdx b/_blogposts/archive/2020-03-26-generalize-uncurry.mdx
similarity index 86%
rename from _blogposts/archive/generalize-uncurry.mdx
rename to _blogposts/archive/2020-03-26-generalize-uncurry.mdx
index d583eeb0e..ff35f0321 100644
--- a/_blogposts/archive/generalize-uncurry.mdx
+++ b/_blogposts/archive/2020-03-26-generalize-uncurry.mdx
@@ -2,7 +2,6 @@
author: hongbo
date: "2020-03-26"
previewImg:
-category: compiler
title: Generalized Uncurry Support in 7.3
description: |
---
@@ -34,7 +33,7 @@ BuckleScript does tons of optimizations and very aggressive arity inference so t
However, such optimization does not apply to high order functions:
```reason
-let highOrder = (f,a,b)=> f (a, b)
+let highOrder = (f,a,b)=> f (a, b)
// can not infer the arity of `f` since we know
// nothing about the arity of `f`, unless
// we do the whole program optimization
@@ -49,24 +48,24 @@ When we create bindings for high order functions in the JS world, we would like
## Generalized uncurried calling convention in this release
-Before release 7.3, we had introduced uncurried calling convention, however, it has serious limitations -- uncurried functions can not be polymorphic, it does not support labels, the error
+Before release 7.3, we had introduced uncurried calling convention, however, it has serious limitations -- uncurried functions can not be polymorphic, it does not support labels, the error
message leaks the underlying encoding -- now all those limitations are gone!
**Previously:**
-
+
-
+
-
+
-The error messages above are cryptic and hard to understand. And the limitation of not supporting recursive functions make uncurried support pretty weak.
+The error messages above are cryptic and hard to understand. And the limitation of not supporting recursive functions make uncurried support pretty weak.
Now those limitations are all gone, you can have polymorphic uncurried recursive functions and it support labels.
-
+
-
+
The error message is also enhanced significantly
@@ -112,7 +111,7 @@ The new error message:
Error: This function is a curried function where an uncurried function is expected
```
-### When arity mismatch
+### When arity mismatch
```reason
let add = (. x, y ) => x + y;
diff --git a/_blogposts/archive/bucklescript-release-7-3.mdx b/_blogposts/archive/2020-04-13-bucklescript-release-7-3.mdx
similarity index 93%
rename from _blogposts/archive/bucklescript-release-7-3.mdx
rename to _blogposts/archive/2020-04-13-bucklescript-release-7-3.mdx
index d89ffb3e6..7be10a2aa 100644
--- a/_blogposts/archive/bucklescript-release-7-3.mdx
+++ b/_blogposts/archive/2020-04-13-bucklescript-release-7-3.mdx
@@ -1,9 +1,6 @@
---
author: hongbo
date: "2020-04-13"
-previewImg: https://res.cloudinary.com/dmm9n7v9f/image/upload/v1587472539/Reason%20Association/reasonml.org/reasonml_art1_1280_zfwnyo.png
-articleImg: https://res.cloudinary.com/dmm9n7v9f/image/upload/v1587024325/Reason%20Association/reasonml.org/jessica-knowlden-WVC6iAZHP0k-unsplash_t86jzt.jpg
-category: compiler
badge: release
title: Announcing BuckleScript 7.3
description: |
@@ -36,7 +33,7 @@ For uncurried support, we also fixed a long standing
inference follows naturally using the new encoding.
```reason
-bar
+bar
-> Belt.Array.mapU((.b)=>b.foo /*no type annotation needed */)
```
@@ -56,7 +53,7 @@ enhancement.
let log = x => Js.log(x)
```
-The generated code used to be
+The generated code used to be
```js
function log(x){
@@ -65,7 +62,7 @@ function log(x){
}
```
-It's now
+It's now
```js
function log(x){
@@ -79,7 +76,7 @@ We have increased the readability of the generated code in several common
places, we believe that we reached *an important milestone* that if you write
code using features that have counterparts in JS, the generated code is
readable. This is not a small achievement given that quite a lot of the
-compiler code base is shared between native backend and JS backend.
+compiler code base is shared between native backend and JS backend.
There are some features that are not available in JS, for example, complex
pattern matches, the readability of those pieces of generated code will
@@ -110,7 +107,7 @@ function popUndefined(s) {
+ s.root = x.tail;
+ return x.head;
}
-
+
}
```
@@ -216,7 +213,7 @@ Below are similar diffs benefiting from such enhancement:
swapUnsafe(xs, i, Js_math.random_int(i, len));
}
- return /* () */0;
-+
++
}
```
diff --git a/_blogposts/archive/a-story-of-exception-encoding.mdx b/_blogposts/archive/2020-05-06-a-story-of-exception-encoding.mdx
similarity index 96%
rename from _blogposts/archive/a-story-of-exception-encoding.mdx
rename to _blogposts/archive/2020-05-06-a-story-of-exception-encoding.mdx
index ffb1dca1d..065681d34 100644
--- a/_blogposts/archive/a-story-of-exception-encoding.mdx
+++ b/_blogposts/archive/2020-05-06-a-story-of-exception-encoding.mdx
@@ -1,8 +1,7 @@
---
author: hongbo
-date: "2020-05-06 18:00"
+date: "2020-05-06"
previewImg:
-category: compiler
title: New Exception Encoding in BuckleScript
description: |
Highlights of our newest changes to the internal representation of exceptions
@@ -15,7 +14,7 @@ We just recently made some significant improvements with our new exception encod
The new encoding allows us to provide proper, clear stacktrace information whenever a Reason/OCaml exception is thrown. This is particularly important when you have some code running in production that needs to collect those stacktrace for diagnostics.
-What's the difference?
+What's the difference?
```reason
exception My_exception { x : int};
@@ -33,7 +32,7 @@ loop ();
When we compile and run this piece of code with the old exception encoding, this is what we'd get:
```
-exn_demo$node src/exn_demo.bs.js
+exn_demo$node src/exn_demo.bs.js
/Users/hongbozhang/git/exn_demo/src/exn_demo.bs.js:11
throw [
@@ -82,7 +81,7 @@ exception B
`exception B` is just the identity block.
-The identity block is an array of 2 slots. The first slot is a string like "B", while the second slot is a unique integer.
+The identity block is an array of 2 slots. The first slot is a string like "B", while the second slot is a unique integer.
In more detail, the native array will also have a magic tag 248 attached which is not relevant for our purposes though.
## What's the new exception encoding?
@@ -129,7 +128,7 @@ Here is an example on how you'd access the exception value within a Reason `try`
```reason
try (someJSFunctionThrowing()) {
-| Not_found => .. // catch reasonml exception 1
+| Not_found => .. // catch reasonml exception 1
| Invalid_argument => // catch reasonml exception 2
| Js.Exn.Error (obj) => ... // catch js exception
}
@@ -146,6 +145,6 @@ The `obj` value in the `Js.Exn.Error` branch is an opaque type to maintain type
## Bonus
Now with our new exception encoding in place, a hidden feature called [extensible variant](https://caml.inria.fr/pub/docs/manual-ocaml/extensiblevariants.html) suddenly got way more interesting as well. Practically speaking, native exceptions are actually a special form of an extensible variant, so both are benefiting from the same representation changes!
-
+
Happy hacking and we would like your feedback!
diff --git a/_blogposts/archive/state-of-reasonml-org-2020-q2-pt1.mdx b/_blogposts/archive/2020-05-06-state-of-reasonml-org-2020-q2-pt1.mdx
similarity index 92%
rename from _blogposts/archive/state-of-reasonml-org-2020-q2-pt1.mdx
rename to _blogposts/archive/2020-05-06-state-of-reasonml-org-2020-q2-pt1.mdx
index f02a3d069..1e37bdedc 100644
--- a/_blogposts/archive/state-of-reasonml-org-2020-q2-pt1.mdx
+++ b/_blogposts/archive/2020-05-06-state-of-reasonml-org-2020-q2-pt1.mdx
@@ -1,9 +1,8 @@
---
author: ryyppy
date: "2020-05-06"
-previewImg: https://res.cloudinary.com/dmm9n7v9f/image/upload/v1588759056/Reason%20Association/reasonml.org/state-of-reasonml-org-q2-2020_ngvmtc.jpg
-articleImg: https://res.cloudinary.com/dmm9n7v9f/image/upload/v1588599051/Reason%20Association/reasonml.org/state-of-reasonml-pt1-hero_m3n6wy.jpg
-category: docs
+previewImg: /static/blog/archive/state-of-reasonml-org-q2-2020.jpg
+articleImg: /static/blog/archive/state-of-reasonml-pt1-hero.jpg
title: State of reasonml.org 2020-Q2 / Pt. 1
description: |
A report on recent achievements in the reasonml.org project and what
@@ -51,7 +50,7 @@ Building a documentation platform for a whole language ecosystem involves a lot
### The Structure and Design
The initial work was mostly about understanding the information architecture, relevant documentation dependencies, and finding all the relevant resources across different websites and blog posts. We have also spent a great amount of time finding a proper design language to visually codify different areas of the platform into a distinctive color scheme.
-\nThe function `f` must have a return type of `option<'b>`.\n\n## Examples\n\n```rescript\nlet addIfAboveOne = value =>\n if (value > 1) {\n Some(value + 1)\n } else {\n None\n }\n\nBelt.Option.flatMap(Some(2), addIfAboveOne) /* Some(3) */\n\nBelt.Option.flatMap(Some(-4), addIfAboveOne) /* None */\n\nBelt.Option.flatMap(None, addIfAboveOne) /* None */\n```" + ], + "signature": "let flatMap: (option<'a>, 'a => option<'b>) => option<'b>" + }, + { + "id": "Belt.Option.getWithDefault", + "kind": "value", + "name": "getWithDefault", + "docstrings": [ + "If `optionalValue` is `Some(value)`, returns `value`, otherwise default.\n\n## Examples\n\n```rescript\nBelt.Option.getWithDefault(None, \"Banana\") /* Banana */\n\nBelt.Option.getWithDefault(Some(\"Apple\"), \"Banana\") /* Apple */\n```\n\n```rescript\nlet greet = (firstName: option