Is export a key word in rescript?

a-c-sreedhar-reddy · December 30, 2020, 12:20pm

reason-association/genType/blob/cfb0ba558347ad7f5a46c84fac89056847bb8edd/examples/typescript-react-example/src/Hooks.res#L54


    export make = (~vehicle) => <div> {React.string("Another Hook " ++ vehicle.name)} </div>

    @react.component
    export anotherComponent = (~vehicle) =>
      <div> {React.string("Another Hook " ++ vehicle.name)} </div>
  }
}

module NoProps = {
  @react.component
  export make = () => <div> ReasonReact.null </div>
}

type cb = (~_to: vehicle) => unit

export functionWithRenamedArgs = (~_to, ~_Type, ~cb: cb) => {
  cb(~_to)
  _to.name ++ _Type.name
}

@react.component

Is export a keyword in rescript?

amiralies · December 30, 2020, 1:48pm

export is a keyword and it’s related to gentype iirc
I’m not sure but I think

export a = 2

is equivalent to

@genType
let a = 2

ryyppy · January 5, 2021, 4:55pm

I have the urge to explain what was going on here: So yes, there are some pretty early experiments for an export keyword to have tighter integration with genType, but those experiments are still ongoing, and not relevant for now.

This feature is by no means supposed to be exposed already, it unintentionally snuck through the release wrap-up. GenType’s example codebase is a pretty important testing ground for all kinds of features, so I am not surprised it was covered in there.

In an upcoming ReScript release the export syntax will be hidden again and your code will reprint back to @genType annotated let bindings (no breaking changes).