Skip to content
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

Refactor source code structure about syntax #433

Merged
merged 3 commits into from
Nov 24, 2024
Merged

Refactor source code structure about syntax #433

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7388931
Split impl fmt::Display to a separate module
magicant Nov 24, 2024
f39b9b3
Redefine MaybeLiteral::extend_if_literal as extend_literal
magicant Nov 24, 2024
c064990
Extract syntax type conversions into a separate module
magicant Nov 24, 2024
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: 6 additions & 0 deletions yash-syntax/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- The `parser::Parser::case_item` and `syntax::CaseItem::from_str` methods
now consume a trailing terminator token, if any. The terminator can be
not only `;;`, but also `;&`, `;|`, or `;;&`.
- In the `syntax::MaybeLiteral` trait, the `extend_if_literal` method is
replaced with the `extend_literal` method, which now takes a mutable reference
to an `Extend<char>` object, instead of an ownership of it. The method may
leave intermediate results in the `Extend<char>` object if unsuccessful.
- The `syntax::NotLiteral` struct is added to represent the case where the
method is unsuccessful.

## [0.12.1] - 2024-11-10

Expand Down
Loading
Loading