Conversation

Would you rather have a library that has excellent type inference, but might require a bit of busywork, or would you prefer a library that gets out of the way but occasionally has worse type errors?

Type inference
59%
Ease of use
41%

227 votesFinal results

cybersyx

@cyberglot

Apr 16, 2020

I don’t think we can choose here 😭😭😭 ease of use first if maintainers are willing to write good docs and tutorials.

GIF

0ch4rl3s.nfo

@acid2

Apr 16, 2020

I wish we could have both! Unfortunately it comes down good inference coming from: class Foo a b | a -> b, b -> a But this has knock-on effects for some other stuff. Hard to fit the nuances into a tweet, so wanted to gauge the room!

Replying to

and

How does it look if you used an associated type for b instead of using a functional dependency? Ie. class Foo a where type B a :: Type I mainly program in Rust, and that's the tool we normally reach for (not having functional deps) 😅

10:49 AM · Apr 16, 2020Twitter Web App

Replying to

and

That is the same as just removing one direction of the FD (knowing a you know b, but associated types aren't injective)