Support extract-module-statements
attribute in juvix code blocks
#2734
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 adds support for the
extract-module-statements
attribute for Juvix code blocks:So if you write something like the following block in a Juvix markdown file:
The statement
type T := t;
from the body of the module is rendered in the output. Themodule Foo;
, andend;
lines are not rendered in the output.A block with the
extract-module-statements
must contain a single local module statement and nothing else. An error is reported if this is not the case.The
extract-module-statements
attribute also takes an optional argument. It sets the number of statements from the module body to drop from the output.In the following example, the output will contain the single line
a : T := t;
.