or: Static Analysis of nil Values in Ruby Code used in YaST.
YaST is written in Ruby. A large part of the code is Ruby that was
transpiled from the YCP language during the YCP Killer project.
To preserve behavior in various edge-case situations, mostly when nil
was passed around, helper libraries were used.
The resulting code is often long and hard to work with.
Example from SlideShow.rb:
total_time = Ops.add( total_time, Ops.divide(Ops.get_integer(stage, "value", 0), 3495) )
The plan is to find patterns in Y2R-generated code which can
be safely translated into more native Ruby code and translate them. In many
cases this will require proving that the edge cases mentioned above can't
happen (e.g. that passed parameters can't be nil
). This will be done using
static analysis on the code.
We have started this during HackWeek 11 with the Zombie Killer project, but did not finish back then.
Since that time, we started using RuboCop in the team to keep a consistent code style. It is a natural match to bring RuboCop and Zombie Killer together, since both are based on the Parser library. RuboCop-YaST was started by Ladislav Slezak, but Zombie Killer is not fully integrated and working.
During HackWeek 13 the goal is to have a safely working RuboCop-YaST that is able to resocialize some zombies in production code.
This project is part of:
Hack Week 13
Activity
Comments
Similar Projects
Catalog/Online Store for a bakery in Rails 7 by gfilippetti
[comment]: # (Please use the project descriptio...
Dawnscanner: parsing a simple sinatra application by pperego
[comment]: # (Please use the project descriptio...
Modernize SCC Customer Management and/or Patchfinder by digitaltomm
[comment]: # (Please use the project descriptio...
Reduce the amount of TODOs for RuboCop in OBS by enavarro_suse
Project Description
The OBS project has a...
Tungsten: A low-level LLVM programming language by mfriedrich
Project Description
> Tungsten is suppose...
SMTGCC by fkastl
[comment]: # (Please use the project descriptio...