Jeff Gentry
Jeff Gentry
On paper, this is what the Struct use case is intended to handle. In @nh13's case, it's just a struct with a single member
meta-comment (pardon the pun). If we're going to start building out the meta sections, is it worth rethinking them altogether, from the perspective of "are these the right thing?". I...
@jayrbolton I haven't come across anything but agree. If you have thoughts I'd encourage you to bring up the topic on the [mailing list]([email protected]). I'd normally suggest a PR but...
`left`/`right` always struck me as being too tied to Scala's `Either` (where I also dislike the `left`/`right` terminology).
@TedBrookings This has come up a few times in the past. If it is something you'd like to see I'd encourage a PR against the spec
This might be where @jdidion was heading all along but I like his proposal as it makes a path towards more general ADTs easier if that ever was a desire
`Pair` was never intended to be the final word. The origin of it was really the need for a tuple construct, but the driving use case at the time only...
I'm curious what other folks think here. Traditionally we've taken the stance to not retroactively fix issues like this - i.e. official versions of the spec aren't living documents.That does...
@jdidion likewise
I think as long as 2 of the 3 have support it's fine to go forward