06:17 <Sergio965> Hey all! I tried writing a simple variant type (type maybe 'a = | Some 'a | None) but I get "invalid module item".

06:18 <Sergio965> That's the only thing I have in the file. What am I missing?

06:19 <Sergio965> Oh, hmm.

06:19 <Sergio965> Nevermind. Looks like refmt is failing with "Fatal error: exception Not_found"

06:28 <Sergio965> Bummer. Guess there's no way to run rebuild without refmt?

06:32 <Sergio965> Oh, I see. refmt is everything.

06:32 <bsansouci> missing semi coloin?

06:32 <bsansouci> missing semi colon*

06:34 <Sergio965> Weird. I removed the #0.0.6 from the pinning and it seemed to work.

06:34 <Sergio965> (Rather, it works)

06:36 <bsansouci> type maybe 'a = | Some of 'a | None

06:36 <bsansouci> Need an `of` keyword ^

06:39 <Sergio965> Not in Reason though, right?...

06:39 <schmave> Originally it needed of, even in reason, not sure if they fixed that in a more recent version

06:40 <schmave> https://github.com/facebook/reason/issues/491

06:40 <Sergio965> Seems to work okay.

06:41 <schmave> Looks like they might have finally pushed the change on June 8th, so in master but not released yet https://github.com/facebook/reason/commit/20ac378109a61cf7f42f22bcb5e8b62fc4ec2278

06:42 <Sergio965> Ah..I see.

06:42 <Sergio965> That would explain exactly what I saw, then.

06:42 <Sergio965> The docs should say something about this....

06:43 <Sergio965> Is there no let _ in _ in reason?

06:44 <bsansouci> The docs correspond to master... The opam version is still 0.0.6

06:44 <bsansouci> Nope, semi colons at the end instead of "in"

06:44 <Sergio965> I mean, when I want to bind a variable only inside a scope.

06:44 <Sergio965> I need to do { let _ ; ... }?

06:45 <bsansouci> What do you mean inside a scope?

06:45 <bsansouci> what ocaml code do you want?

06:45 <Sergio965> So, I'm trying to do: print_string switch x { ... }, but this doesn't work. I have to do print_string (switch x { ... }).

06:45 <Sergio965> I thought maybe doing: let s = switch x { ... } in print_string s would work, but it doesn't.

06:47 <bsansouci> you do need parens to help indicate precedence. If you want to bind the return of the switch only to be used by the print_string right under and nothing else, you can nest them in curly braces

06:47 <bsansouci> `{

06:47 <bsansouci> let s = switch x { ... };

06:47 <bsansouci> print_string s;

06:47 <bsansouci> };`

06:48 <Sergio965> But isn't `switch` a keyword?

06:48 <Sergio965> Should `switch ...` all be a single unit?

06:50 <bsansouci> ¯\_(ツ)_/¯

06:51 <Sergio965> Haha

06:51 <Sergio965> Alrighty. :)

07:00 <chenglou> Sergio965: https://github.com/facebook/reason/wiki/Newcomer-Tips-&-Tricks

07:00 <chenglou> this should help big time

19:24 <grandy____> hello, just curios how close reason is to being something I could use for a simple react app ?

19:29 <grandy____> (or is it perhaps something I could use now by targeting js) ...

19:30 <bsansouci> grandy____: hey!

19:30 <grandy____> hello!

19:31 <bsansouci> I think a lot of stuff needs to be figured out... i.e.: there is only one exploration that I know of: https://github.com/fxfactorial/ocaml-reactjs

19:32 <grandy____> bsansouci: ahh ok, cool...

19:33 <grandy____> bsansouci: going to be keeping an eye on reason, as it appears to be addressing most of the things I want :)

19:33 <bsansouci> What are the things you want? :D

19:35 <grandy____> bsansouci: the ability to target js and native platforms, and all the type system / functional stuff from ocaml .. using flow + immutable.js + invariant is cool but it feels heavy compared to something like reason

19:36 <bsansouci> Do you use react native right now?

19:38 <grandy____> bsansouci: yep

19:47 <Sergio965> Are there API docs somewhere?

19:47 <Sergio965> Or is there nothing added to the OCaml stdlibs?

19:48 <bsansouci> Nothing's added so far from what I know, you can use the normal stdlib