-
Notifications
You must be signed in to change notification settings - Fork 37
[Merged by Bors] - generated_quantities and fix for #167 #168
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
Conversation
devmotion
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments 🙂
Co-authored-by: David Widmann <[email protected]>
devmotion
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I guess you can trigger bors, and then we could make a new release with both this and the other PR (if tests of both are successful)?
|
I guess we keep the name |
Great! What do I do?!
Sure 👍 We can easily deprecate and rename later if people find it more confusing than helpful. |
|
bors +r |
|
Did you mean "r+"? |
|
bors r+ |
|
Am I doing this correctly @devmotion ? I THINK I've now "queued" both PRs, so bors will now check if they're compatible by putting them into staging branch? |
|
Yes, that's fine. bors puts them in a queue and checks them in a separate staging branch (and hopefully) merges on after another into master, with the second PR taking into account the changes of the first one. |
This PR adds `generated_quantities` as discussed in TuringLang/Turing.jl#1335 + adds a fix for #167.
|
Pull request successfully merged into master. Build succeeded: |
This PR adds
generated_quantitiesas discussed in TuringLang/Turing.jl#1335 + adds a fix for #167.