-
The current design is nonsensical. With some future-Rust features, we could have:
``` rust
pub trait EntryMap: Map {
type Occupied: Vacant;
fn entry Entry>;
}
pub enum Entry
where
O: Oc…
-
My might say that `dry-python/returns` is one of the most typing-intensive project in Python-land.
It might be a good idea to add some expert-level koans about it. Like:
- Working with monads
- D…
-
@belevy proposed a concept in #5 which parameterizes each field by a type constructor - this allows anyone to promote a plain Haskell record into an HKD record.
This has the form:
```haskell
n…
-
Thanks for the wonderful library!
Would you consider generalizing this beyond error-handling and and threading any monadic context?
I had written something similar for Optional types. Such that …
-
For higher-kinded types:
```scala
$ cat x.scala
import language.higherKinds
trait Dist[Z] { self =>
def sample[CC[A] : Nothing : [A]Nothing
-
Right now the "aliases" are always of the same type, for every field in a record.
But what if, instead of having a fixed type, we had a type constructor wrapping each particular field's type? Very …
-
Not an issue per se, I was trying to do the same proof of concept as you did, but for TypeScript.
Wondering how could the generators work so well for Promises (async/await in TS transpiles into gen…
-
The compiler rejects the following,
```scala
object Test {
trait Foo[T]
trait Bar[T]
implicit val foobar: Foo[Int] & Bar[Int] = ???
trait Quux[F[_]]
implicit def quux[F[_]](impl…
-
Instead of having to type `t(Maybe, int)` or `t(Either, "a", str)`, it would be much cleaner to type `Maybe(int)` or `Either("a", str)`.
This should be relatively easy to implement, though it would …
-
I find myself wanting to be able to Typeable quantify over higher-kinded variables, like `* -> *` or `Constraint`. This problem comes in two parts: one of them I've thought a lot about and I'm pretty …