Point out issue with failing user builds due to syntax errors#965
Merged
emilio merged 1 commit intomozilla:masterfrom May 26, 2024
Merged
Point out issue with failing user builds due to syntax errors#965emilio merged 1 commit intomozilla:masterfrom
emilio merged 1 commit intomozilla:masterfrom
Conversation
This is a trap "for young players" and loosing feedback from rustc or your favorite code analysis tools won't make things better. Let's point out the issue and the solution given in issue mozilla#472 upfront.
sirhcel
force-pushed
the
nonfatal-parsing-in-docs
branch
from
2a52b57 to
00170e6
Compare
sirhcel
changed the title
emilio
approved these changes
May 26, 2024
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
2 participants
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 is a trap "for young players" and loosing feedback from rustc or your favorite code analysis tools won't make things better. Let's point out the issue and the solution given in issue #472 upfront.