-
Notifications
You must be signed in to change notification settings - Fork 20
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
Safe tactic calls for Restate
#118
Safe tactic calls for Restate
#118
Conversation
I did run scalaFix T_T |
Anyhow, making this a draft while I add some tests for the modified tactics as well. |
That took less time than I expected |
Ah! I think the confusion comes from having both a Restate and a Rewrite tactic, when they do the same thing. Restate take into account both Rewrite and RewriteTrue, depending on the number of parameters, but does not catch error. Can you maybe merge the three tactic (Restate, Rewrite, RewriteTrue) into a single one with the two adequate apply functions? |
The new Some of the other tactics call |
Funny how and when issues manifest themselves #119 |
Yeah, I think keeping all three is confusing and a waste of space since they do the exact same thing. Moreover Rewrite should be renamed Restate anyway |
Provided the build passes soon, we should merge this for now. Since |
Ok let's merge that for now and I'll deal with the issue soon. |
Added
unwrapTactic
calls toRestate
, as before this it had raw calls to kernel tactics, which subsequently raised kernel errors whenever it failed.Also added
RewriteTrue
as aBasicStepTactic
, since it didn't exist before, and was required for this.