Closed mooreryan closed 1 year ago
Also related, from this GitHub issue:
I don't advice using custom for common cases, it's easier to stick to tuples.
So, combining what you said there with the "unstable" note in the docs, is it safe to say that custom
will be removed in a future release?
You are right. It has been around for a long time without a need for reversion, and people are using it anyway.
In the mli docs, there is a note that says that this function "should be considered experimental and may be revised or removed in a future version". I checked the git blame and that warning has been in the docs for ~5 years, so can we assume that it is no longer unstable? Also, I the 2.0.0 issue didn't mention anything about it, so just wanted to check.
(Related issue)