Turing v0.36 and removal of Pathfinder code #579
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Oh no, something about the new Gibbs is failing 😓 |
penelopeysm
force-pushed
the
mhauru/0.36-gibbs
branch
2 times, most recently
from
56b03a4 to
40ed08a
Compare
|
Preview the changes: https://turinglang.org/docs/pr-previews/579 |
penelopeysm
approved these changes
Jan 28, 2025
|
Thanks for fixing this! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes two unrelated changes:
These are in the same PR, because doing the first one made us realise that having Pathfinder as dependency is annoying: We couldn't upgrade Turing.jl to v0.36 because there was not yet a version of Pathfinder that included it in its compat, and we thus couldn't build docs for the latest version of our own package.