Re:The Hardest Program I've Ever Written (2015)
by blt on Tuesday August 22, 2017 @01:25AM
(#15069929)
An active learning approach would be cool, where the formatter process a large corpus of code and asks a human operator for advice when it is especially uncertain about the best place to split.
Even if training the splitting policy from scratch is too hard, learning would be a good way to establish cost weights on different kinds of rule violations.
For example, one could use a subset of the Linux kernel source code as training, and another (unseen) subset as testing.
Highly rated projects on github might work too.