fix(lexer): Don't require frontmatters to be escaped with indented fences by epage · Pull Request #145754 · rust-lang/rust (original) (raw)

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 andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation6 Commits1 Checks10 Files changed

Conversation

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

[ Show hidden characters]({{ revealButtonHref }})

@epage

The RFC only limits hyphens at the beginning of lines and not if they are indented or embedded in other content.

Sticking to that approach was confirmed by the T-lang liason at #141367 (comment)

There is a regression in error message quality which I'm leaving for someone if they feel this needs improving.

Tracking issue: #136889

Fixes #141367

@rustbot

r? @SparrowLii

rustbot has assigned @SparrowLii.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added S-waiting-on-review

Status: Awaiting review from the assignee but also interested parties.

T-compiler

Relevant to the compiler team, which will review and decide on the PR/issue.

labels

Aug 22, 2025

@epage epage mentioned this pull request

Aug 22, 2025

14 tasks

@rustbot

This comment has been minimized.

@epage

…nces

The RFC only limits hyphens at the beginning of lines and not if they are indented or embedded in other content.

Sticking to that approach was confirmed by the T-lang liason at rust-lang#141367 (comment)

There is a regression in error message quality which I'm leaving for someone if they feel this needs improving.

@rustbot

This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

SparrowLii

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@SparrowLii

@bors

📌 Commit 142e25e has been approved by SparrowLii

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors

Status: Waiting on bors to run and complete tests. Bors will change the label on completion.

and removed S-waiting-on-review

Status: Awaiting review from the assignee but also interested parties.

labels

Sep 1, 2025

bors added a commit that referenced this pull request

Sep 1, 2025

@bors

Rollup of 5 pull requests

Successful merges:

r? @ghost @rustbot modify labels: rollup

rust-timer added a commit that referenced this pull request

Sep 1, 2025

@rust-timer

Rollup merge of #145754 - epage:escape, r=SparrowLii

fix(lexer): Don't require frontmatters to be escaped with indented fences

The RFC only limits hyphens at the beginning of lines and not if they are indented or embedded in other content.

Sticking to that approach was confirmed by the T-lang liason at #141367 (comment)

There is a regression in error message quality which I'm leaving for someone if they feel this needs improving.

Tracking issue: #136889

Fixes #141367

github-actions bot pushed a commit to model-checking/verify-rust-std that referenced this pull request

Sep 9, 2025

@bors

Rollup of 5 pull requests

Successful merges:

r? @ghost @rustbot modify labels: rollup

@epage epage mentioned this pull request

Sep 16, 2025

11 tasks

@epage epage mentioned this pull request

Oct 23, 2025

10 tasks

Labels

F-frontmatter

`#![feature(frontmatter)]`

S-waiting-on-bors

Status: Waiting on bors to run and complete tests. Bors will change the label on completion.

T-compiler

Relevant to the compiler team, which will review and decide on the PR/issue.