Benjamin San Souci
Benjamin San Souci
That really doesn't need to be the case. We should make them case insensitive but warn maybe?
not sure if we should track it down and fix. It'd be nice though.
Right now we add the `-I` flags for everything I think, that could cause weird issues. The ppx should be totally isolated.
Right now we just assume the user has opam installed with `4.02.3+buckle-master` as the compiler. We should check and error when it's not the case.
This is a pretty important thing for folks who want to use bsb-native and would like opam users to use their libraries. I think right now you can't publish a...
This is a problem in OCaml 4.02.3. I think there's a fix (kinda thought we fixed this). ``` ~/Desktop/tmp/example2 master* ❯ time ~/Desktop/bucklescript/lib/bsb -backend bytecode ninja: Entering directory `lib/bs/bytecode' [4/4]...
Right now, if you have reason-cli you'll get this error ``` ❯ ./node_modules/.bin/bsb -make-world ninja: Entering directory `lib/bs/bytecode' [2/2] Building src/index.mlast.d [1/2] Building src/index.cmo FAILED: src/index.cmo src/index.cmi ocamlfind ocamlc -I...
We currently implement namespace using module aliasing. We generate a binary ML file that we compile each time bsb is ran. We should avoid this.
I'll start with a small explanation and we'll go from there. [Esy](https://github.com/esy/esy)'s a package manager for Reason. It allows using any build system to build packages, as long as the...
Right now you have to dig into `./lib/bs/bytecode/index.byte` for example. That's a bit annoying and hidden for newcomers. Maybe just having a simple symlink would help.