DeedleFake

It would also be nice if the interface said what version it was displaying docs for, possibly with the ability to pull up the docs for specific versions as well.

@fenrirstrife What I've resorted to for now is just copying and pasting what I need everywhere, and then treating it as `dynamic` in the code that needs to deal with...

> Agree. Would you like to contribute this change? Thanks 🙏 Certainly. What error should it return?

> The only surprising aspect is that MarshalText would usually take precedence over MarshalScalar. I think that's up to the encoding package in question. The proposal seems to just be...

As far as channels specifically go, no I don't think so, but I think the generic usage is the most important part of this one. I was primarily inspired by...

Yes, I believe so. See https://en.wikipedia.org/wiki/Variadic_template. The Go draft proposal for generics also lists > No variadic type parameters. There is no support for variadic type parameters, which would permit...

I've been thinking about what functionality would be required at a minimum for `[T ...]` to be useful. The list I have currently is * `a = b` where `a`...

> I think it could be pretty confusing to have a construct like var val T in your example code create multiple variables. It never would, though. In all cases...

The `...` syntax is a placeholder. It reads just fine with a predefined identifier: ```go func Thunk[I various, O various](func(I) O) func(I) O func FoldMap[I various, A various](func(I) A, ...func(A)...

In the current design, yes, but only the variant mentioned that uses a comparison function, not the one with the `comparable` constraint. For example, ```go type Metric[T ...] struct {...