12/19/2023 0 Comments Ucsd final draft software![]() ![]() Refinements they contain to correctly checks other downstream programs Īt this point, the content of the liquid-* packages is considered "trusted" and "frozen", until you won't ![]() Things like liquid-prelude or liquidhaskell are compiled at least once, as we would need the Without specifying any extra environment variables from the command line. To begin with, perform a full build of all the libraries, by doing either cabal v2-build or stack build, Of any of the liquid-* ancillary library in dev mode, so that rebuilds only affect the In other terms, we explicitly disable recompilation "static assets", avoiding the need for a recompilation. On the assumption that most changes to the liquidhaskell library do not alter the validity ofĪlready-checked libraries, and therefore things like liquid-prelude can be considered To mitigate this, we offer a faster, "dev-style" build mode which is based Therefore every time the latter changes, an expensive rebuild of those packages is triggered, which Using a fully-fledged GHC plugin doesn't help in this sense,īecause packages like liquidhaskell or liquid-prelude have a direct dependency on liquidhaskell-boot, and Only the bare minimum, to try out new ideas. ![]() When working on the liquidhaskell-boot library, usually all we want is to make changes and quickly recompile General Development Guideįor those diving into the implementation of LiquidHaskell, here are a few tips: Fast (re)compilation If you have further questions or you just need help, you can always reach out on our slack channel, google groups mailing list, GitHub issue tracker, or by emailing Ranjit Jhala, Niki Vazou. Pull requests don't just have to be about code: documentation can often be improved too! Ask for Help options.md, specifications.md, the main tutorial (as relevant) If you're making user-visible changes, please also add documentation.show new features that that are supported or how it fixes some previous issue Please be sure to include test cases that illustrate the effect of the PR.Please create pull requests against the develop branch.We are thrilled to get PRs! Please follow these guidelines, as doing so will increase the chances of Please, let us know which liquidhaskell version you are using.Write down the expected behaviour vs the actual behaviour.Provide a small Haskell file producing the issue.State as clearly as possible what is the problem you are facing.If something doesn't work as it should, please consider opening a github issue This is an open-source project, and we love getting feedback (and patches)! Reporting a Bug If you're a LiquidHaskell user (or just curious), you probably want to go to the documentation website instead. This is the development site of the LiquidHaskell formal verification tool. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |