Skip to content

Conversation

cristianoc
Copy link
Collaborator

Based on #777 but where unhurried is turned off.

@@ -918,13 +918,13 @@ Path Js.n
"label": "nullable",
"kind": 22,
"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",
Copy link
Collaborator Author

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.

Copy link
Member

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...

Copy link
Collaborator Author

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

Copy link
Member

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 😀

@cristianoc cristianoc requested a review from zth May 26, 2023 01:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants