Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Fix the level of headings #516

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.

Sign up for GitHub

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
yui-knk merged 1 commit into from
Jan 21, 2025
Merged

Fix the level of headings #516

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions NEWS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

## Lrama 0.7.0 (2025-01-21)

## [EXPERIMENTAL] Support the generation of the IELR(1) parser described in this paper
### [EXPERIMENTAL] Support the generation of the IELR(1) parser described in this paper

Support the generation of the IELR(1) parser described in this paper.
https://www.sciencedirect.com/science/article/pii/S0167642309001191
Expand All @@ -15,12 +15,12 @@ If you use IELR(1) parser, you can write the following directive in your grammar

But, currently IELR(1) parser is experimental feature. If you find any bugs, please report it to us. Thank you.

## Support `-t` option as same as `--debug` option
### Support `-t` option as same as `--debug` option

Support to `-t` option as same as `--debug` option.
These options align with Bison behavior. So same as `--debug` option.

## Trace only explicit rules
### Trace only explicit rules

Support to trace only explicit rules.
If you use `--trace=rules` option, it shows include mid-rule actions. If you want to show only explicit rules, you can use `--trace=only-explicit-rules` option.
Expand Down
Loading