000218350 001__ 218350
000218350 005__ 20190317000440.0
000218350 037__ $$aREP_WORK
000218350 245__ $$aStyle Checking With Scala.Meta
000218350 269__ $$a2015
000218350 260__ $$c2015
000218350 300__ $$a23
000218350 336__ $$aReports
000218350 520__ $$aIn many companies, code reviews are big parts of the day-to-day life of an engineer. Some can argue that the time spent on someone else’s code is time that some cannot spent on her or his own work. Code reviews usually allow to find two kinds of issues. The first kind consists of high-level design errors compared to the specifications of the program while the second type consists of style problems. In this report, we argue that the search of the later kind of error can be automated, as the set of style issues is usually well defined for a programming language. We propose modifications to a linter tool called Obey, which allows to analyze Abstract Syntax Trees of Scala code, raise warnings and suggest changes that can be automatically persisted. Over the course of this project we worked jointly with Codacy, a company proposing automated code reviews, to have an industrial application which would allow users to define their own set of rules. This report also presents the results of this real life testing.
000218350 6531_ $$aStyle Checking
000218350 6531_ $$aAutomated Code Review
000218350 6531_ $$aCode Inference
000218350 6531_ $$aMetaprogramming
000218350 700__ $$aDemarne, Mathieu
000218350 700__ $$0246182$$aBurmako, Eugene$$g214505
000218350 8564_ $$s691393$$uhttps://infoscience.epfl.ch/record/218350/files/StyleCheckingWithScalaMeta.pdf$$yn/a$$zn/a
000218350 909C0 $$0252187$$pLAMP$$xU10409
000218350 909CO $$ooai:infoscience.tind.io:218350$$pIC$$preport$$qGLOBAL_SET
000218350 917Z8 $$x214505
000218350 937__ $$aEPFL-REPORT-218350
000218350 973__ $$aEPFL
000218350 980__ $$aREPORT