- Notifications
You must be signed in to change notification settings - Fork61
Turn off uncurried#778
New issue
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
| "tags": [], | ||
| "detail": "type nullable<+'a>", | ||
| "documentation":{"kind": "markdown", "value": "\n A value of this type can be undefined,null or 'a. This type is equivalent to Js.Null_undefined.t.\n"} | ||
| "detail": "type nullable<'a> = Value('a) | Null | Undefined", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
@zth we lost the+ here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Right, that's... weird. Don't think we changed the+ in the implementation...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Looks like this is the intended printing, inherited from OCaml, which only prints the+ when the type is abstract:
#type 'a t1;;type'a t1#type+'a t2;;type+'a t2#type+'a t2= |A;;type'a t2=A
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Interesting! That's good to know 😀
Based on#777 but where unhurried is turned off.