Skip to content
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

Remove crucible-mc? #1122

Closed
langston-barrett opened this issue Nov 7, 2023 · 2 comments · Fixed by #1164
Closed

Remove crucible-mc? #1122

langston-barrett opened this issue Nov 7, 2023 · 2 comments · Fixed by #1164

Comments

@langston-barrett
Copy link
Contributor

There doesn't seem to be much content there. Any thoughts @yav?

@RyanGlScott
Copy link
Contributor

I recall that @Ptival was looking into reviving this at some point, but I don't know what became of that.

@Ptival
Copy link
Contributor

Ptival commented Nov 7, 2023

There are two crucible-mcs:

  • The one merged into the master branch, that is very barebones and was created by Iavor 4 years ago. I doubt it's ever going to be useful in the present state, and so likely could be removed (with @yav 's confirmation).

  • The one stuck in the longstanding crucible-mc branch. This one I wrote under Aaron Tomb's supervision about 2-3 years ago, and is more fleshed out. As I recall, we were able to export some Crucible ASTs (under some restrictions) into transition systems that we could export into Sally syntax to run the model checker on. I'm not aware of any interest in reviving this one, it's also likely bitrotting. Not sure how I feel about it, merging it would add a bit of maintenance overhead that may be useful to no one, but throwing it away sounds wasteful. Open to discussion.

langston-barrett added a commit to langston-barrett/crucible that referenced this issue Jan 18, 2024
langston-barrett added a commit that referenced this issue Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants