is it part of a project we can read about?
Do you want to make compiler error messages better? We're doing an analysis of (type) error messages for #ocaml -- if you have a moment (or 10), we'd love for you to help out by participating!
http://dijkstra.eecs.umich.edu/~endremad/George_HumanStudy1/ …
(RT would be most appreciated!)
-
-
-
This study is part of a follow on to this paper from 2017; we're still working on the new one will post when ready! http://eric.seidel.io/pub/nate-oopsla17.pdf …
Kraj razgovora
Novi razgovor -
-
-
@MattWindsor91 you might like this -
Tweet je nedostupan.
Novi razgovor -
-
-
a lot of errors seems to be confusing * with *., 4 with 4.0, @ with ::, etc. It might be good to build some statistical model to try out alternatives. (Heck, just getting floating point and list will cover a huge amount of case).
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
That was pretty interesting. It made me really appreciate two things about Haskell: type signatures for function definitions and not having semicolons and statements :). I had forgotten just how annoying it was to rely on type inference alone, without type signatures to help.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Amazing
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.