mirror of
https://github.com/ruby/ruby.git
synced 2022-11-09 12:17:21 -05:00
71344a1d63
It is unclear why this was implemented, I assume it was for performance back in 2006. However today, this compression defeats bytecode caching entirely and end up being counter productive. https://github.com/ruby/racc/commit/ae3703c1d0 |
||
|---|---|---|
| .. | ||
| cadenza | ||
| cast | ||
| csspool | ||
| edtf | ||
| huia | ||
| journey | ||
| liquor | ||
| machete | ||
| mediacloth | ||
| mof | ||
| namae | ||
| nasl | ||
| nokogiri-css | ||
| opal | ||
| php_serialization | ||
| README.txt | ||
| riml | ||
| ruby18 | ||
| ruby22 | ||
| tp_plus | ||
| twowaysql | ||
These files are "known-good" compiler output, generated from a stable version of Racc. Whenever Racc is refactored, or changes are made which should not affect the compiler output, running "rake test" checks that the compiler output is exactly the same as these files. If a change is made which *should* change the compiler output, these files will have to be regenerated from the source in test/assets, and the results committed.