-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chore/update latest rascal release #18
Chore/update latest rascal release #18
Conversation
@mahills could you have a quick look at these changes. I may have accepted them without too much scrutiny and merged in the interest of the Rascal release. Rodin was asking for a peek by us. Much obliged! |
I'll take a look, but it may take a couple of days. |
The one to remove a doubly-defined function is fine. I'm guessing code got merged in there from another module. That module honestly was a bit of a mess and needed some serious refactoring anyway. I think those functions were just sanity checks added while that module was being built -- it was part of the code for the ISSTA 2013 paper, but that is actually hosted here: https://github.com/PLSE-Lab/issta-2013 |
The commit to fix the constructor name is also fine. It had been named |
For the commit to remove a code clone, the three functions do different things, but were written in a lazy way (by me) and could be written in a better way using an optional filter. I don't think these were being used, but may have appeared in older code repos that were made available as artifacts for papers. If we need these, we can put them back. We aren't really tracking stats like this anymore since this required manually updating a spreadsheet, now we extract them automatically (and don't include the PHP version number, which required manual inspection), so we won't miss these going forwards. |
Okay, so I think that's all of them, I got curious so I just looked now, but if I need to look at something else please let me know! |
Updated to
rascal
: 0.40.17rascal-maven-plugin
: 0.28.9The updated type checker identified some issues: