Sorry for the delay. It has been a very interesting week in the low level implementation of Racket. A few days ago, Matthew fixed the bug and enabled the new expander, and then he fixed most of the problems that appear with the changes. So now looks like a good time to retry all the tests and see if the test are working with the snapshot version of Racket.
Following this idea, I remembered that the rackjure project ( https://github.com/greghendershott/rackjure ) has a .travis.yml file, to get continuous integration tests in Travis. It uses a trick to run the project with the latest 10 versions of Racket. You can configure it to run less versions, for example only 6.0.1, 6.1.1 and HEAD (but allow errors in HEAD). You should look at the file in the repository because it's very clear, and if you have a problem you may ask the author because he usually reads the list. This will give you a report of the errors that the next version of Racket would create, and you can send an early warning to the list. This will be helpfull to fix the errors before shipping. Gustavo On Wed, Jul 15, 2015 at 4:14 AM, Ryan Davis <zenspi...@gmail.com> wrote: > >> On Jul 14, 2015, at 20:19, Gustavo Massaccesi <gust...@oma.org.ar> wrote: >> >> Replacing the line 1758 of optimize.c >> >> - if ((info->inline_fuel < 0) && info->has_nonleaf && !noapp) >> + if ((info->inline_fuel <= 0) && info->has_nonleaf && !noapp) >> >> make the problem disappear, but I still don't understand why "(dup >> rep)" is the only combination that creates a problem. >> >> I also want to think about the "(info->inline_fuel >= 0)" in line 1872 >> and how that interacts with the "if (noapp)" in line 1876 ... > > Thanks! I can test against my whole suite in tomorrow's daily if you'd like. > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
