Hi Jon,

Allow me to brainstorm with you. I don't know what is done in the context of code metrics for Haskell programs, but you could try to find correlations (of their lack thereof) between metrics such as (cyclomatic complexity, fan-in/fan-out) and bugs. For this you could use the Github repositories. The number of bugs would have to be normalized using the numbers of users of a project (maybe measured in number of downloads).

Just an idea...

On Thu, Aug 4, 2016 at 10:15 PM, Jon Kristensen <info@jonkri.org> wrote:

Hi, everyone!

I'm looking for a master thesis topic that is empirical in nature (like, statistics, hypothesis testing, etc.).

The work could involve analyzing either package metadata (Cabal information), code (AST), and/or data from some other source, possibly comparing similar data from some non-Haskell domain.

As an example, one idea that was suggested to me was to look at usage aggregation, or like, how much of a given package another package is actually using (which could be relevant in any orphan-instance discussion).

>From an academic standpoint, it would be good to pick a metric that can be validated in some way.

Thank you!

Best,
Jon
_______________________________________________
Haskell-Cafe mailing list
To (un)subscribe, modify options or view archives go to:
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
Only members subscribed via the mailman list are allowed to post.