Make = "" optional in reason syntax

[bobzhang]

[@bs.obj]
external bsObjMake: (~comment: string=?, ~platform: string, unit) => _ = "";

it would be nice to just have

[@bs.obj]
external bsObjMake: (~comment: string=?, ~platform: string, unit) => _  ;

[baransu]

Would it behave the same for all external? With [@bs.obj] it makes sense to omit = „” but with other cases like actual bindings I have strong feelings about not using = „” at all. It’s one of the common bug sources in my team. Someone changes external fn name and runtime errors pops up :/

[bobzhang]

@baransu I agree with you that not using = "" in most cases except bs.obj. And we are going to warn users when seeing ="". For bs.obj, it has to be an empty string.
There are other attributes which expect to be empty strings, bs.get_idex, bs.set_index

[jordwalke]

I could also see this being useful if someone made a ppx plugin for automatically creating c bindings or bindings to other languages. Good first task as it's pretty easy.