We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We currently have the following special directives for external function definitions:
@return(nullable) external someFunc1: unit => option<string> = "someFunc" @return(null_undefined_to_opt) external someFunc2: unit => option<string> = "someFunc" @return(undefined_to_opt) external someFunc3: unit => option<string> = "someFunc" @return(null_to_opt) external someFunc4: unit => option<string> = "someFunc"
The text was updated successfully, but these errors were encountered:
Actually @return(undefined_to_opt) is useful to ensure nested options work correctly, see also the discussion in #7054 and #7430.
@return(undefined_to_opt)
It is currently used in Js.Array(2) for example.
Js.Array(2)
Sorry, something went wrong.
No branches or pull requests
Uh oh!
There was an error while loading. Please reload this page.
We currently have the following special directives for external function definitions:
The text was updated successfully, but these errors were encountered: