-
Notifications
You must be signed in to change notification settings - Fork 32
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
[Merged by Bors] - Hotfixes after #309 #351
Closed
Closed
Changes from 11 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
ecf1e5d
attempt at fixing error doctest
torfjelde 917334b
Update src/submodel_macro.jl
torfjelde 29d692a
capture return-value in submodel
torfjelde 73962ad
Merge branch 'tor/submodels-hotfixes' of github.com:TuringLang/Dynami…
torfjelde 9ee336b
formatting and added test for return-value and submodel
torfjelde ce0a3e8
fixed typo
torfjelde 59303d7
fix CI so as to not break poor bors
torfjelde 274aebb
added docfilter for nested LoadError
torfjelde ef0faa5
Update docs/make.jl
torfjelde 9ecb939
fixed doctestfilter
torfjelde c4e91a0
added LoadError doctest filter to tests
torfjelde 9b32797
improved the LoadError filter
torfjelde ad049c2
updated turing tests compat bound
torfjelde File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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.
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.
I like returning both the
retval
andvarinfo
. I was talking with Philip that we should consider enforcing this more systematically. Roughly speaking, we can consider adopting the notation thatretval
refers to generated quantities andvarinfo
refers to model parameters. This would help clarify the submodel notation as well, i.e.x = SubModel
will extractretval
and assign it to LHSx ~ SubModel
will extractvarinfo
and assign it to LHSFollowing this view, we no longer need to concern ourselves what is the semantics if the returned value
retval
ofSubModel
is deterministic in case 2.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.
I'm a bit confused. In both those cases we still have to concern ourselves with the return-value, no? Essentially the difference between
=
and~
will be whether we have$retval
orvarinfo
below, right?Anyways, you're happy with this right? You're just talking about potentially also supporting
~
later?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.
yes, happy with this PR.
I think
retval
andvarinfo
provides a clear semantical distinction between=
and~
. If we always return both, (e.g. we can return(, varinfo)
in caseretval
is empty), we can extract eitherretval
orvarinfo
for=
or~
.