Giter VIP home page Giter VIP logo

Comments (9)

Casteran avatar Casteran commented on September 27, 2024 1

from hydra-battles.

Zimmi48 avatar Zimmi48 commented on September 27, 2024 1

Sounds good to me.

from hydra-battles.

palmskog avatar palmskog commented on September 27, 2024 1

@Casteran I agree in general, but I think it's fine to change statements and module names conservatively as long as pull requests are submitted to the goedel repo in reasonable time (so that each Coq stable version has a working release of the incompleteness theorem).

from hydra-battles.

Zimmi48 avatar Zimmi48 commented on September 27, 2024

Yes, I agree that it would make sense to copy just these three files as it would cut the dependency on pocklington.

from hydra-battles.

Casteran avatar Casteran commented on September 27, 2024

@Zimmi48 @palmskog
Te branch with-ackermann has been made quickly (by naively copying files). It iits structure is OK, there should exist
a way to move these files from a project to another ?

from hydra-battles.

Zimmi48 avatar Zimmi48 commented on September 27, 2024

Yes, there are tricks to move files while keeping the git history thanks to git subtree.

from hydra-battles.

palmskog avatar palmskog commented on September 27, 2024

It's fine by me to move the Ackermann library to hydra-battles for easier development, but at the same time I believe:

  • we should leave the rest of Gödel's incompleteness theorem in the goedel repo, not least for visibility reasons - this is basically an important Coq formalization milestone that should be easy to locate
  • we should make sure the goedel repo and package can build properly with hydra-battles as a dependency
  • we should preserve the history of the Ackermann library via git subtree

How does that sound to you @Zimmi48?

from hydra-battles.

Casteran avatar Casteran commented on September 27, 2024

@palmskog @Zimmi48

Perhaps the (present and future) maintainers of hydra-battles should follow the following politics

  • add doc, bullets, etc, to the historical modules of Ackermann
  • do not modify statements, implicit arguments, names of these modules,
  • useful changes may be done in new modules, not required by Goedel

We may write such a warning in the README

from hydra-battles.

palmskog avatar palmskog commented on September 27, 2024

I think we can close this issue now, please reopen if it becomes relevant again.

from hydra-battles.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.