-
I understand your decision, to not use operator overloading.
To frame my following opposition to it, here my background:
I can not use FSharp in my current project, since it is barely implemented.…
-
Doesn't matter how many positional arguments I pass to "ReactDOMRe.Style.make", the result will always be something like:
`makeStyle(undefined, undefined, undefined, undefined, undefined, undefined, …
-
In React we can handle this by React Error Boundaries.
https://reactjs.org/docs/error-boundaries.html
Something similar can be done here too to catch the error if any chunk fails.
-
I learned that using pipe last operator (`|>`) is discouraged when compiling to JS.
Quoting @ryyppy
> the conclusion for when to use pipe-first / pipe-last is: if you are using ocaml, you might w…
-
I am getting this issue when compiling on ubuntu/darwin with bucklescript 7.3.1
### steps
```
npx bs-platform -init my-react-app -theme react-hooks
cd my-react-app/
docker run -it --rm --name…
-
Kind of related to https://github.com/reasonml/reason-react/issues/410.
Maybe this is not an actual issue, but a chance to improve documentation.
If one tries to create a component `T` that:
- …
-
The upcoming version of Bucklescript changes the signature of `[||]` from `array('a)` to `array('_weak)` since there were unsoundness issues with `Js.Array.push`. This change makes `array` incompatibl…
-
There has been some more activity on both repos lately.
This includes all changes starting from January 2020
**reasonml.github.io history:**
https://github.com/reasonml/reasonml.github.io/commits…
-
I'd submit a PR but I don't know where you'd want to place this info. If you're writing an ocaml lib that's cross-compatible with native and bucklescript, then these are some docs on how to prevent od…
-
We've noticed while looking at https://github.com/reasonml/reason-react/pull/529 that uncurried functions don't seem to compile as expected when eval'd at a module level. This code will error in a way…