You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
Brendan Zabarauskas@brendanzab·Oct 3, 2017Oh I definitely empathise with that - I spent the day wrangling a dependently typed proof into submission and battilng the horrific errors…1
Brendan Zabarauskas@brendanzab·Oct 3, 2017Not that it's an excuse for poor errors, but I feel like it gets easier once you internalise the rules of a specific type system though.1
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
Brendan Zabarauskas@brendanzab·Oct 3, 2017Pretty amazing what the human mind can do, but as somebody with a design background it pains me deeply to see.11
Brendan Zabarauskas@brendanzab·Oct 3, 2017But as a type system implementer I know just how challenging implementing good error reporting is. It's effort well spent though.1
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
Brendan Zabarauskas@brendanzabReplying to @logaanDefinitely. Stack traces are much easier to implement because a concrete counter-example should be immediately visible to the author.10:39 AM · Oct 3, 2017·Twitter Web Client
Brendan Zabarauskas@brendanzab·Oct 3, 2017Replying to @brendanzab and @logaanGranted, Elixir's errors were tableflippingly atrocious for the longest time 🤦♂️