Repository navigation
Document how to format Stan files that use #include - #881
Merged
WardBrian merged 1 commit intoNov 16, 2026
Merged
Conversation
Signed-off-by: Soujas K <kudchadkarsoujas@gmail.com>
This file contains hidden or 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
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.
Fixes #853
Submission Checklist
Summary
Documents how to use format_stan_file with Stan programs that use #include:
With CmdStan 2.40 two or more includes format fine, so the canonicalize=includes workaround from the issue is not needed anymore (stanc3#1621 is fixed).
Added test_model_format_includes using the existing bernoulli_include.stan. test_compilation.py passes locally with CmdStan 2.40 (11 passed), black/isort/flake8 clean.
AI assistance: I used an AI assistant to help reproduce the issue and draft the change. I reviewed the code and ran the tests myself.
Copyright and Licensing
Copyright holder: Soujas K
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses: