Skip to content

Add typo suggestion for a misspelt Cargo environment variable - #148559

Merged
bors merged 1 commit into
rust-lang:masterfrom
chenyukang:yukang-fix-148439-env
Nov 7, 2025
Merged

Add typo suggestion for a misspelt Cargo environment variable#148559
bors merged 1 commit into
rust-lang:masterfrom
chenyukang:yukang-fix-148439-env

Conversation

@chenyukang

@chenyukangchenyukang commented Nov 6, 2025

Copy link
Copy Markdown
Member

Fixes#148439

@rustbotrustbot 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 Nov 6, 2025
@rustbot

Copy link
Copy Markdown
Collaborator

r? @fee1-dead

rustbot has assigned @fee1-dead.
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

@rust-log-analyzer

This comment has been minimized.

@chenyukang
chenyukangforce-pushed the yukang-fix-148439-env branch 2 times, most recently from 48c2fbb to 1f8b6daCompareNovember 6, 2025 04:14
Comment on lines +187 to +189
const KNOWN_CARGO_VARS: &[&str] = &[
// List of known Cargo environment variables that are set for crates (not build scripts, OUT_DIR etc).
// See: https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-crates

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Discussion (non-blocking): I have two reservations about making this suggestion:

  1. Wouldn't this depend on the specific cargo version?
  2. Basically, what I was trying to get at, is that in principle I feel like rustc should not make assumptions about cargo (that is, rustc should not "know" about cargo's existence), because cargo isn't the only way to invoke rustc.

I guess I could be convinced by "well, most users do build with cargo", so don't consider this a hard-blocking concern.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

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

  1. I'm not sure, there is a similar list for this in rust-analyzer: https://github.com/chenyukang/rust/blob/702bf000a0b5062d8b5ced717a26d70919df6ba0/src/tools/rust-analyzer/crates/project-model/src/env.rs#L9-L49 , I guess there is a better and general way to keep it synced.
  2. I agree rustc should not knowing details about cargo, I think it's ok since we need to check the prefix with CARGO_ of env:
    https://github.com/rust-lang/rust/pull/148559/files#diff-0eaa1095d59f2f3d9c015005d15fd8f7cda13121a8404d77b2955fc5fcd40449R213, and it's a note but not code suggestions, it's maybe incorrect for rare scenarios.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Yeah, seems alright, was just curious to hear what you think.

Comment threadcompiler/rustc_builtin_macros/messages.ftl Outdated
@rust-log-analyzer

This comment has been minimized.

@KivooeoKivooeo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Comment threadcompiler/rustc_builtin_macros/src/env.rs Outdated
Comment threadtests/ui/env-macro/env-cargo-var-typo-issue-148439.rs
Comment threadcompiler/rustc_builtin_macros/src/env.rs
@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@Kivooeo

Copy link
Copy Markdown
Member

@bors r+

@bors

bors commented Nov 6, 2025

Copy link
Copy Markdown
Collaborator

📌 Commit 3edd25f has been approved by Kivooeo

It is now in the queue for this repository.

@borsbors 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 Nov 6, 2025
@jhprattjhpratt mentioned this pull request Nov 7, 2025
bors added a commit that referenced this pull request Nov 7, 2025
Rollup of 12 pull requests
Successful merges:
- #145768 (Offload device)
- #145992 (Stabilize `vec_deque_pop_if`)
- #147416 (Early return if span is from expansion so we dont get empty span and ice later on)
- #147808 (btree: cleanup difference, intersection, is_subset)
- #148520 (style: Use binary literals instead of hex literals in doctests for `highest_one` and `lowest_one`)
- #148559 (Add typo suggestion for a misspelt Cargo environment variable)
- #148567 (Fix incorrect precedence caused by range expression)
- #148570 (Fix mismatched brackets in generated .dir-locals.el)
- #148575 (fix dev guide link in rustc_query_system/dep_graph/README.md)
- #148578 (core docs: add notes about availability of `Atomic*::from_mut_slice`)
- #148603 (Backport 1.91.1 relnotes to main)
- #148609 (Sync str::rsplit_once example with str::split_once)
r? `@ghost`
`@rustbot` modify labels: rollup
@bors
bors merged commit 3186f21 into rust-lang:masterNov 7, 2025
11 checks passed
@rustbotrustbot added this to the 1.93.0 milestone Nov 7, 2025
rust-timer added a commit that referenced this pull request Nov 7, 2025
Rollup merge of #148559 - chenyukang:yukang-fix-148439-env, r=Kivooeo
Add typo suggestion for a misspelt Cargo environment variable
Fixes#148439
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Misleading suggestion when using env!() on a misspelt Cargo environment variable

8 participants

@chenyukang@rustbot@rust-log-analyzer@Kivooeo@bors@Urgau@jieyouxu@fee1-dead
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Add typo suggestion for a misspelt Cargo environment variable by chenyukang · Pull Request #148559 · rust-lang/rust · GitHub
Skip to content

Add typo suggestion for a misspelt Cargo environment variable - #148559

Merged
bors merged 1 commit into
rust-lang:masterfrom
chenyukang:yukang-fix-148439-env
Nov 7, 2025
Merged

Add typo suggestion for a misspelt Cargo environment variable#148559
bors merged 1 commit into
rust-lang:masterfrom
chenyukang:yukang-fix-148439-env

Conversation

@chenyukang

@chenyukangchenyukang commented Nov 6, 2025

Copy link
Copy Markdown
Member

Fixes#148439

@rustbotrustbot 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 Nov 6, 2025
@rustbot

Copy link
Copy Markdown
Collaborator

r? @fee1-dead

rustbot has assigned @fee1-dead.
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

@rust-log-analyzer

This comment has been minimized.

@chenyukang
chenyukangforce-pushed the yukang-fix-148439-env branch 2 times, most recently from 48c2fbb to 1f8b6daCompareNovember 6, 2025 04:14
Comment on lines +187 to +189
const KNOWN_CARGO_VARS: &[&str] = &[
// List of known Cargo environment variables that are set for crates (not build scripts, OUT_DIR etc).
// See: https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-crates

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Discussion (non-blocking): I have two reservations about making this suggestion:

  1. Wouldn't this depend on the specific cargo version?
  2. Basically, what I was trying to get at, is that in principle I feel like rustc should not make assumptions about cargo (that is, rustc should not "know" about cargo's existence), because cargo isn't the only way to invoke rustc.

I guess I could be convinced by "well, most users do build with cargo", so don't consider this a hard-blocking concern.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

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

  1. I'm not sure, there is a similar list for this in rust-analyzer: https://github.com/chenyukang/rust/blob/702bf000a0b5062d8b5ced717a26d70919df6ba0/src/tools/rust-analyzer/crates/project-model/src/env.rs#L9-L49 , I guess there is a better and general way to keep it synced.
  2. I agree rustc should not knowing details about cargo, I think it's ok since we need to check the prefix with CARGO_ of env:
    https://github.com/rust-lang/rust/pull/148559/files#diff-0eaa1095d59f2f3d9c015005d15fd8f7cda13121a8404d77b2955fc5fcd40449R213, and it's a note but not code suggestions, it's maybe incorrect for rare scenarios.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Yeah, seems alright, was just curious to hear what you think.

Comment threadcompiler/rustc_builtin_macros/messages.ftl Outdated
@rust-log-analyzer

This comment has been minimized.

@KivooeoKivooeo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Comment threadcompiler/rustc_builtin_macros/src/env.rs Outdated
Comment threadtests/ui/env-macro/env-cargo-var-typo-issue-148439.rs
Comment threadcompiler/rustc_builtin_macros/src/env.rs
@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@Kivooeo

Copy link
Copy Markdown
Member

@bors r+

@bors

bors commented Nov 6, 2025

Copy link
Copy Markdown
Collaborator

📌 Commit 3edd25f has been approved by Kivooeo

It is now in the queue for this repository.

@borsbors 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 Nov 6, 2025
@jhprattjhpratt mentioned this pull request Nov 7, 2025
bors added a commit that referenced this pull request Nov 7, 2025
Rollup of 12 pull requests
Successful merges:
- #145768 (Offload device)
- #145992 (Stabilize `vec_deque_pop_if`)
- #147416 (Early return if span is from expansion so we dont get empty span and ice later on)
- #147808 (btree: cleanup difference, intersection, is_subset)
- #148520 (style: Use binary literals instead of hex literals in doctests for `highest_one` and `lowest_one`)
- #148559 (Add typo suggestion for a misspelt Cargo environment variable)
- #148567 (Fix incorrect precedence caused by range expression)
- #148570 (Fix mismatched brackets in generated .dir-locals.el)
- #148575 (fix dev guide link in rustc_query_system/dep_graph/README.md)
- #148578 (core docs: add notes about availability of `Atomic*::from_mut_slice`)
- #148603 (Backport 1.91.1 relnotes to main)
- #148609 (Sync str::rsplit_once example with str::split_once)
r? `@ghost`
`@rustbot` modify labels: rollup
@bors
bors merged commit 3186f21 into rust-lang:masterNov 7, 2025
11 checks passed
@rustbotrustbot added this to the 1.93.0 milestone Nov 7, 2025
rust-timer added a commit that referenced this pull request Nov 7, 2025
Rollup merge of #148559 - chenyukang:yukang-fix-148439-env, r=Kivooeo
Add typo suggestion for a misspelt Cargo environment variable
Fixes#148439
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Misleading suggestion when using env!() on a misspelt Cargo environment variable

8 participants

@chenyukang@rustbot@rust-log-analyzer@Kivooeo@bors@Urgau@jieyouxu@fee1-dead
, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Add typo suggestion for a misspelt Cargo environment variable by chenyukang · Pull Request #148559 · rust-lang/rust · GitHub
Skip to content

Add typo suggestion for a misspelt Cargo environment variable - #148559

Merged
bors merged 1 commit into
rust-lang:masterfrom
chenyukang:yukang-fix-148439-env
Nov 7, 2025
Merged

Add typo suggestion for a misspelt Cargo environment variable#148559
bors merged 1 commit into
rust-lang:masterfrom
chenyukang:yukang-fix-148439-env

Conversation

@chenyukang

@chenyukangchenyukang commented Nov 6, 2025

Copy link
Copy Markdown
Member

Fixes#148439

@rustbotrustbot 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 Nov 6, 2025
@rustbot

Copy link
Copy Markdown
Collaborator

r? @fee1-dead

rustbot has assigned @fee1-dead.
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

@rust-log-analyzer

This comment has been minimized.

@chenyukang
chenyukangforce-pushed the yukang-fix-148439-env branch 2 times, most recently from 48c2fbb to 1f8b6daCompareNovember 6, 2025 04:14
Comment on lines +187 to +189
const KNOWN_CARGO_VARS: &[&str] = &[
// List of known Cargo environment variables that are set for crates (not build scripts, OUT_DIR etc).
// See: https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-crates

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Discussion (non-blocking): I have two reservations about making this suggestion:

  1. Wouldn't this depend on the specific cargo version?
  2. Basically, what I was trying to get at, is that in principle I feel like rustc should not make assumptions about cargo (that is, rustc should not "know" about cargo's existence), because cargo isn't the only way to invoke rustc.

I guess I could be convinced by "well, most users do build with cargo", so don't consider this a hard-blocking concern.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

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

  1. I'm not sure, there is a similar list for this in rust-analyzer: https://github.com/chenyukang/rust/blob/702bf000a0b5062d8b5ced717a26d70919df6ba0/src/tools/rust-analyzer/crates/project-model/src/env.rs#L9-L49 , I guess there is a better and general way to keep it synced.
  2. I agree rustc should not knowing details about cargo, I think it's ok since we need to check the prefix with CARGO_ of env:
    https://github.com/rust-lang/rust/pull/148559/files#diff-0eaa1095d59f2f3d9c015005d15fd8f7cda13121a8404d77b2955fc5fcd40449R213, and it's a note but not code suggestions, it's maybe incorrect for rare scenarios.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Yeah, seems alright, was just curious to hear what you think.

Comment threadcompiler/rustc_builtin_macros/messages.ftl Outdated
@rust-log-analyzer

This comment has been minimized.

@KivooeoKivooeo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Comment threadcompiler/rustc_builtin_macros/src/env.rs Outdated
Comment threadtests/ui/env-macro/env-cargo-var-typo-issue-148439.rs
Comment threadcompiler/rustc_builtin_macros/src/env.rs
@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@Kivooeo

Copy link
Copy Markdown
Member

@bors r+

@bors

bors commented Nov 6, 2025

Copy link
Copy Markdown
Collaborator

📌 Commit 3edd25f has been approved by Kivooeo

It is now in the queue for this repository.

@borsbors 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 Nov 6, 2025
@jhprattjhpratt mentioned this pull request Nov 7, 2025
bors added a commit that referenced this pull request Nov 7, 2025
Rollup of 12 pull requests
Successful merges:
- #145768 (Offload device)
- #145992 (Stabilize `vec_deque_pop_if`)
- #147416 (Early return if span is from expansion so we dont get empty span and ice later on)
- #147808 (btree: cleanup difference, intersection, is_subset)
- #148520 (style: Use binary literals instead of hex literals in doctests for `highest_one` and `lowest_one`)
- #148559 (Add typo suggestion for a misspelt Cargo environment variable)
- #148567 (Fix incorrect precedence caused by range expression)
- #148570 (Fix mismatched brackets in generated .dir-locals.el)
- #148575 (fix dev guide link in rustc_query_system/dep_graph/README.md)
- #148578 (core docs: add notes about availability of `Atomic*::from_mut_slice`)
- #148603 (Backport 1.91.1 relnotes to main)
- #148609 (Sync str::rsplit_once example with str::split_once)
r? `@ghost`
`@rustbot` modify labels: rollup
@bors
bors merged commit 3186f21 into rust-lang:masterNov 7, 2025
11 checks passed
@rustbotrustbot added this to the 1.93.0 milestone Nov 7, 2025
rust-timer added a commit that referenced this pull request Nov 7, 2025
Rollup merge of #148559 - chenyukang:yukang-fix-148439-env, r=Kivooeo
Add typo suggestion for a misspelt Cargo environment variable
Fixes#148439
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Misleading suggestion when using env!() on a misspelt Cargo environment variable

8 participants

@chenyukang@rustbot@rust-log-analyzer@Kivooeo@bors@Urgau@jieyouxu@fee1-dead
, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Add typo suggestion for a misspelt Cargo environment variable by chenyukang · Pull Request #148559 · rust-lang/rust · GitHub
Skip to content

Add typo suggestion for a misspelt Cargo environment variable - #148559

Merged
bors merged 1 commit into
rust-lang:masterfrom
chenyukang:yukang-fix-148439-env
Nov 7, 2025
Merged

Add typo suggestion for a misspelt Cargo environment variable#148559
bors merged 1 commit into
rust-lang:masterfrom
chenyukang:yukang-fix-148439-env

Conversation

@chenyukang

@chenyukangchenyukang commented Nov 6, 2025

Copy link
Copy Markdown
Member

Fixes#148439

@rustbotrustbot 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 Nov 6, 2025
@rustbot

Copy link
Copy Markdown
Collaborator

r? @fee1-dead

rustbot has assigned @fee1-dead.
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

@rust-log-analyzer

This comment has been minimized.

@chenyukang
chenyukangforce-pushed the yukang-fix-148439-env branch 2 times, most recently from 48c2fbb to 1f8b6daCompareNovember 6, 2025 04:14
Comment on lines +187 to +189
const KNOWN_CARGO_VARS: &[&str] = &[
// List of known Cargo environment variables that are set for crates (not build scripts, OUT_DIR etc).
// See: https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-crates

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Discussion (non-blocking): I have two reservations about making this suggestion:

  1. Wouldn't this depend on the specific cargo version?
  2. Basically, what I was trying to get at, is that in principle I feel like rustc should not make assumptions about cargo (that is, rustc should not "know" about cargo's existence), because cargo isn't the only way to invoke rustc.

I guess I could be convinced by "well, most users do build with cargo", so don't consider this a hard-blocking concern.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

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

  1. I'm not sure, there is a similar list for this in rust-analyzer: https://github.com/chenyukang/rust/blob/702bf000a0b5062d8b5ced717a26d70919df6ba0/src/tools/rust-analyzer/crates/project-model/src/env.rs#L9-L49 , I guess there is a better and general way to keep it synced.
  2. I agree rustc should not knowing details about cargo, I think it's ok since we need to check the prefix with CARGO_ of env:
    https://github.com/rust-lang/rust/pull/148559/files#diff-0eaa1095d59f2f3d9c015005d15fd8f7cda13121a8404d77b2955fc5fcd40449R213, and it's a note but not code suggestions, it's maybe incorrect for rare scenarios.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Yeah, seems alright, was just curious to hear what you think.

Comment threadcompiler/rustc_builtin_macros/messages.ftl Outdated
@rust-log-analyzer

This comment has been minimized.

@KivooeoKivooeo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Comment threadcompiler/rustc_builtin_macros/src/env.rs Outdated
Comment threadtests/ui/env-macro/env-cargo-var-typo-issue-148439.rs
Comment threadcompiler/rustc_builtin_macros/src/env.rs
@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@Kivooeo

Copy link
Copy Markdown
Member

@bors r+

@bors

bors commented Nov 6, 2025

Copy link
Copy Markdown
Collaborator

📌 Commit 3edd25f has been approved by Kivooeo

It is now in the queue for this repository.

@borsbors 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 Nov 6, 2025
@jhprattjhpratt mentioned this pull request Nov 7, 2025
bors added a commit that referenced this pull request Nov 7, 2025
Rollup of 12 pull requests
Successful merges:
- #145768 (Offload device)
- #145992 (Stabilize `vec_deque_pop_if`)
- #147416 (Early return if span is from expansion so we dont get empty span and ice later on)
- #147808 (btree: cleanup difference, intersection, is_subset)
- #148520 (style: Use binary literals instead of hex literals in doctests for `highest_one` and `lowest_one`)
- #148559 (Add typo suggestion for a misspelt Cargo environment variable)
- #148567 (Fix incorrect precedence caused by range expression)
- #148570 (Fix mismatched brackets in generated .dir-locals.el)
- #148575 (fix dev guide link in rustc_query_system/dep_graph/README.md)
- #148578 (core docs: add notes about availability of `Atomic*::from_mut_slice`)
- #148603 (Backport 1.91.1 relnotes to main)
- #148609 (Sync str::rsplit_once example with str::split_once)
r? `@ghost`
`@rustbot` modify labels: rollup
@bors
bors merged commit 3186f21 into rust-lang:masterNov 7, 2025
11 checks passed
@rustbotrustbot added this to the 1.93.0 milestone Nov 7, 2025
rust-timer added a commit that referenced this pull request Nov 7, 2025
Rollup merge of #148559 - chenyukang:yukang-fix-148439-env, r=Kivooeo
Add typo suggestion for a misspelt Cargo environment variable
Fixes#148439
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Misleading suggestion when using env!() on a misspelt Cargo environment variable

8 participants

@chenyukang@rustbot@rust-log-analyzer@Kivooeo@bors@Urgau@jieyouxu@fee1-dead
, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' Add typo suggestion for a misspelt Cargo environment variable by chenyukang · Pull Request #148559 · rust-lang/rust · GitHub
Skip to content

Add typo suggestion for a misspelt Cargo environment variable - #148559

Merged
bors merged 1 commit into
rust-lang:masterfrom
chenyukang:yukang-fix-148439-env
Nov 7, 2025
Merged

Add typo suggestion for a misspelt Cargo environment variable#148559
bors merged 1 commit into
rust-lang:masterfrom
chenyukang:yukang-fix-148439-env

Conversation

@chenyukang

@chenyukangchenyukang commented Nov 6, 2025

Copy link
Copy Markdown
Member

Fixes#148439

@rustbotrustbot 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 Nov 6, 2025
@rustbot

Copy link
Copy Markdown
Collaborator

r? @fee1-dead

rustbot has assigned @fee1-dead.
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

@rust-log-analyzer

This comment has been minimized.

@chenyukang
chenyukangforce-pushed the yukang-fix-148439-env branch 2 times, most recently from 48c2fbb to 1f8b6daCompareNovember 6, 2025 04:14
Comment on lines +187 to +189
const KNOWN_CARGO_VARS: &[&str] = &[
// List of known Cargo environment variables that are set for crates (not build scripts, OUT_DIR etc).
// See: https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-crates

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Discussion (non-blocking): I have two reservations about making this suggestion:

  1. Wouldn't this depend on the specific cargo version?
  2. Basically, what I was trying to get at, is that in principle I feel like rustc should not make assumptions about cargo (that is, rustc should not "know" about cargo's existence), because cargo isn't the only way to invoke rustc.

I guess I could be convinced by "well, most users do build with cargo", so don't consider this a hard-blocking concern.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

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

  1. I'm not sure, there is a similar list for this in rust-analyzer: https://github.com/chenyukang/rust/blob/702bf000a0b5062d8b5ced717a26d70919df6ba0/src/tools/rust-analyzer/crates/project-model/src/env.rs#L9-L49 , I guess there is a better and general way to keep it synced.
  2. I agree rustc should not knowing details about cargo, I think it's ok since we need to check the prefix with CARGO_ of env:
    https://github.com/rust-lang/rust/pull/148559/files#diff-0eaa1095d59f2f3d9c015005d15fd8f7cda13121a8404d77b2955fc5fcd40449R213, and it's a note but not code suggestions, it's maybe incorrect for rare scenarios.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Yeah, seems alright, was just curious to hear what you think.

Comment threadcompiler/rustc_builtin_macros/messages.ftl Outdated
@rust-log-analyzer

This comment has been minimized.

@KivooeoKivooeo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Comment threadcompiler/rustc_builtin_macros/src/env.rs Outdated
Comment threadtests/ui/env-macro/env-cargo-var-typo-issue-148439.rs
Comment threadcompiler/rustc_builtin_macros/src/env.rs
@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@Kivooeo

Copy link
Copy Markdown
Member

@bors r+

@bors

bors commented Nov 6, 2025

Copy link
Copy Markdown
Collaborator

📌 Commit 3edd25f has been approved by Kivooeo

It is now in the queue for this repository.

@borsbors 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 Nov 6, 2025
@jhprattjhpratt mentioned this pull request Nov 7, 2025
bors added a commit that referenced this pull request Nov 7, 2025
Rollup of 12 pull requests
Successful merges:
- #145768 (Offload device)
- #145992 (Stabilize `vec_deque_pop_if`)
- #147416 (Early return if span is from expansion so we dont get empty span and ice later on)
- #147808 (btree: cleanup difference, intersection, is_subset)
- #148520 (style: Use binary literals instead of hex literals in doctests for `highest_one` and `lowest_one`)
- #148559 (Add typo suggestion for a misspelt Cargo environment variable)
- #148567 (Fix incorrect precedence caused by range expression)
- #148570 (Fix mismatched brackets in generated .dir-locals.el)
- #148575 (fix dev guide link in rustc_query_system/dep_graph/README.md)
- #148578 (core docs: add notes about availability of `Atomic*::from_mut_slice`)
- #148603 (Backport 1.91.1 relnotes to main)
- #148609 (Sync str::rsplit_once example with str::split_once)
r? `@ghost`
`@rustbot` modify labels: rollup
@bors
bors merged commit 3186f21 into rust-lang:masterNov 7, 2025
11 checks passed
@rustbotrustbot added this to the 1.93.0 milestone Nov 7, 2025
rust-timer added a commit that referenced this pull request Nov 7, 2025
Rollup merge of #148559 - chenyukang:yukang-fix-148439-env, r=Kivooeo
Add typo suggestion for a misspelt Cargo environment variable
Fixes#148439
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Misleading suggestion when using env!() on a misspelt Cargo environment variable

8 participants

@chenyukang@rustbot@rust-log-analyzer@Kivooeo@bors@Urgau@jieyouxu@fee1-dead
, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Add typo suggestion for a misspelt Cargo environment variable by chenyukang · Pull Request #148559 · rust-lang/rust · GitHub
Skip to content

Add typo suggestion for a misspelt Cargo environment variable - #148559

Merged
bors merged 1 commit into
rust-lang:masterfrom
chenyukang:yukang-fix-148439-env
Nov 7, 2025
Merged

Add typo suggestion for a misspelt Cargo environment variable#148559
bors merged 1 commit into
rust-lang:masterfrom
chenyukang:yukang-fix-148439-env

Conversation

@chenyukang

@chenyukangchenyukang commented Nov 6, 2025

Copy link
Copy Markdown
Member

Fixes#148439

@rustbotrustbot 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 Nov 6, 2025
@rustbot

Copy link
Copy Markdown
Collaborator

r? @fee1-dead

rustbot has assigned @fee1-dead.
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

@rust-log-analyzer

This comment has been minimized.

@chenyukang
chenyukangforce-pushed the yukang-fix-148439-env branch 2 times, most recently from 48c2fbb to 1f8b6daCompareNovember 6, 2025 04:14
Comment on lines +187 to +189
const KNOWN_CARGO_VARS: &[&str] = &[
// List of known Cargo environment variables that are set for crates (not build scripts, OUT_DIR etc).
// See: https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-crates

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Discussion (non-blocking): I have two reservations about making this suggestion:

  1. Wouldn't this depend on the specific cargo version?
  2. Basically, what I was trying to get at, is that in principle I feel like rustc should not make assumptions about cargo (that is, rustc should not "know" about cargo's existence), because cargo isn't the only way to invoke rustc.

I guess I could be convinced by "well, most users do build with cargo", so don't consider this a hard-blocking concern.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

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

  1. I'm not sure, there is a similar list for this in rust-analyzer: https://github.com/chenyukang/rust/blob/702bf000a0b5062d8b5ced717a26d70919df6ba0/src/tools/rust-analyzer/crates/project-model/src/env.rs#L9-L49 , I guess there is a better and general way to keep it synced.
  2. I agree rustc should not knowing details about cargo, I think it's ok since we need to check the prefix with CARGO_ of env:
    https://github.com/rust-lang/rust/pull/148559/files#diff-0eaa1095d59f2f3d9c015005d15fd8f7cda13121a8404d77b2955fc5fcd40449R213, and it's a note but not code suggestions, it's maybe incorrect for rare scenarios.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Yeah, seems alright, was just curious to hear what you think.

Comment threadcompiler/rustc_builtin_macros/messages.ftl Outdated
@rust-log-analyzer

This comment has been minimized.

@KivooeoKivooeo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Comment threadcompiler/rustc_builtin_macros/src/env.rs Outdated
Comment threadtests/ui/env-macro/env-cargo-var-typo-issue-148439.rs
Comment threadcompiler/rustc_builtin_macros/src/env.rs
@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@Kivooeo

Copy link
Copy Markdown
Member

@bors r+

@bors

bors commented Nov 6, 2025

Copy link
Copy Markdown
Collaborator

📌 Commit 3edd25f has been approved by Kivooeo

It is now in the queue for this repository.

@borsbors 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 Nov 6, 2025
@jhprattjhpratt mentioned this pull request Nov 7, 2025
bors added a commit that referenced this pull request Nov 7, 2025
Rollup of 12 pull requests
Successful merges:
- #145768 (Offload device)
- #145992 (Stabilize `vec_deque_pop_if`)
- #147416 (Early return if span is from expansion so we dont get empty span and ice later on)
- #147808 (btree: cleanup difference, intersection, is_subset)
- #148520 (style: Use binary literals instead of hex literals in doctests for `highest_one` and `lowest_one`)
- #148559 (Add typo suggestion for a misspelt Cargo environment variable)
- #148567 (Fix incorrect precedence caused by range expression)
- #148570 (Fix mismatched brackets in generated .dir-locals.el)
- #148575 (fix dev guide link in rustc_query_system/dep_graph/README.md)
- #148578 (core docs: add notes about availability of `Atomic*::from_mut_slice`)
- #148603 (Backport 1.91.1 relnotes to main)
- #148609 (Sync str::rsplit_once example with str::split_once)
r? `@ghost`
`@rustbot` modify labels: rollup
@bors
bors merged commit 3186f21 into rust-lang:masterNov 7, 2025
11 checks passed
@rustbotrustbot added this to the 1.93.0 milestone Nov 7, 2025
rust-timer added a commit that referenced this pull request Nov 7, 2025
Rollup merge of #148559 - chenyukang:yukang-fix-148439-env, r=Kivooeo
Add typo suggestion for a misspelt Cargo environment variable
Fixes#148439
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Misleading suggestion when using env!() on a misspelt Cargo environment variable

8 participants

@chenyukang@rustbot@rust-log-analyzer@Kivooeo@bors@Urgau@jieyouxu@fee1-dead
, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Add typo suggestion for a misspelt Cargo environment variable by chenyukang · Pull Request #148559 · rust-lang/rust · GitHub
Skip to content

Add typo suggestion for a misspelt Cargo environment variable - #148559

Merged
bors merged 1 commit into
rust-lang:masterfrom
chenyukang:yukang-fix-148439-env
Nov 7, 2025
Merged

Add typo suggestion for a misspelt Cargo environment variable#148559
bors merged 1 commit into
rust-lang:masterfrom
chenyukang:yukang-fix-148439-env

Conversation

@chenyukang

@chenyukangchenyukang commented Nov 6, 2025

Copy link
Copy Markdown
Member

Fixes#148439

@rustbotrustbot 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 Nov 6, 2025
@rustbot

Copy link
Copy Markdown
Collaborator

r? @fee1-dead

rustbot has assigned @fee1-dead.
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

@rust-log-analyzer

This comment has been minimized.

@chenyukang
chenyukangforce-pushed the yukang-fix-148439-env branch 2 times, most recently from 48c2fbb to 1f8b6daCompareNovember 6, 2025 04:14
Comment on lines +187 to +189
const KNOWN_CARGO_VARS: &[&str] = &[
// List of known Cargo environment variables that are set for crates (not build scripts, OUT_DIR etc).
// See: https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-crates

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Discussion (non-blocking): I have two reservations about making this suggestion:

  1. Wouldn't this depend on the specific cargo version?
  2. Basically, what I was trying to get at, is that in principle I feel like rustc should not make assumptions about cargo (that is, rustc should not "know" about cargo's existence), because cargo isn't the only way to invoke rustc.

I guess I could be convinced by "well, most users do build with cargo", so don't consider this a hard-blocking concern.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

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

  1. I'm not sure, there is a similar list for this in rust-analyzer: https://github.com/chenyukang/rust/blob/702bf000a0b5062d8b5ced717a26d70919df6ba0/src/tools/rust-analyzer/crates/project-model/src/env.rs#L9-L49 , I guess there is a better and general way to keep it synced.
  2. I agree rustc should not knowing details about cargo, I think it's ok since we need to check the prefix with CARGO_ of env:
    https://github.com/rust-lang/rust/pull/148559/files#diff-0eaa1095d59f2f3d9c015005d15fd8f7cda13121a8404d77b2955fc5fcd40449R213, and it's a note but not code suggestions, it's maybe incorrect for rare scenarios.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Yeah, seems alright, was just curious to hear what you think.

Comment threadcompiler/rustc_builtin_macros/messages.ftl Outdated
@rust-log-analyzer

This comment has been minimized.

@KivooeoKivooeo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Comment threadcompiler/rustc_builtin_macros/src/env.rs Outdated
Comment threadtests/ui/env-macro/env-cargo-var-typo-issue-148439.rs
Comment threadcompiler/rustc_builtin_macros/src/env.rs
@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@Kivooeo

Copy link
Copy Markdown
Member

@bors r+

@bors

bors commented Nov 6, 2025

Copy link
Copy Markdown
Collaborator

📌 Commit 3edd25f has been approved by Kivooeo

It is now in the queue for this repository.

@borsbors 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 Nov 6, 2025
@jhprattjhpratt mentioned this pull request Nov 7, 2025
bors added a commit that referenced this pull request Nov 7, 2025
Rollup of 12 pull requests
Successful merges:
- #145768 (Offload device)
- #145992 (Stabilize `vec_deque_pop_if`)
- #147416 (Early return if span is from expansion so we dont get empty span and ice later on)
- #147808 (btree: cleanup difference, intersection, is_subset)
- #148520 (style: Use binary literals instead of hex literals in doctests for `highest_one` and `lowest_one`)
- #148559 (Add typo suggestion for a misspelt Cargo environment variable)
- #148567 (Fix incorrect precedence caused by range expression)
- #148570 (Fix mismatched brackets in generated .dir-locals.el)
- #148575 (fix dev guide link in rustc_query_system/dep_graph/README.md)
- #148578 (core docs: add notes about availability of `Atomic*::from_mut_slice`)
- #148603 (Backport 1.91.1 relnotes to main)
- #148609 (Sync str::rsplit_once example with str::split_once)
r? `@ghost`
`@rustbot` modify labels: rollup
@bors
bors merged commit 3186f21 into rust-lang:masterNov 7, 2025
11 checks passed
@rustbotrustbot added this to the 1.93.0 milestone Nov 7, 2025
rust-timer added a commit that referenced this pull request Nov 7, 2025
Rollup merge of #148559 - chenyukang:yukang-fix-148439-env, r=Kivooeo
Add typo suggestion for a misspelt Cargo environment variable
Fixes#148439
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Misleading suggestion when using env!() on a misspelt Cargo environment variable

8 participants

@chenyukang@rustbot@rust-log-analyzer@Kivooeo@bors@Urgau@jieyouxu@fee1-dead
, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); Add typo suggestion for a misspelt Cargo environment variable by chenyukang · Pull Request #148559 · rust-lang/rust · GitHub
Skip to content

Add typo suggestion for a misspelt Cargo environment variable - #148559

Merged
bors merged 1 commit into
rust-lang:masterfrom
chenyukang:yukang-fix-148439-env
Nov 7, 2025
Merged

Add typo suggestion for a misspelt Cargo environment variable#148559
bors merged 1 commit into
rust-lang:masterfrom
chenyukang:yukang-fix-148439-env

Conversation

@chenyukang

@chenyukangchenyukang commented Nov 6, 2025

Copy link
Copy Markdown
Member

Fixes#148439

@rustbotrustbot 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 Nov 6, 2025
@rustbot

Copy link
Copy Markdown
Collaborator

r? @fee1-dead

rustbot has assigned @fee1-dead.
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

@rust-log-analyzer

This comment has been minimized.

@chenyukang
chenyukangforce-pushed the yukang-fix-148439-env branch 2 times, most recently from 48c2fbb to 1f8b6daCompareNovember 6, 2025 04:14
Comment on lines +187 to +189
const KNOWN_CARGO_VARS: &[&str] = &[
// List of known Cargo environment variables that are set for crates (not build scripts, OUT_DIR etc).
// See: https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-crates

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Discussion (non-blocking): I have two reservations about making this suggestion:

  1. Wouldn't this depend on the specific cargo version?
  2. Basically, what I was trying to get at, is that in principle I feel like rustc should not make assumptions about cargo (that is, rustc should not "know" about cargo's existence), because cargo isn't the only way to invoke rustc.

I guess I could be convinced by "well, most users do build with cargo", so don't consider this a hard-blocking concern.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

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

  1. I'm not sure, there is a similar list for this in rust-analyzer: https://github.com/chenyukang/rust/blob/702bf000a0b5062d8b5ced717a26d70919df6ba0/src/tools/rust-analyzer/crates/project-model/src/env.rs#L9-L49 , I guess there is a better and general way to keep it synced.
  2. I agree rustc should not knowing details about cargo, I think it's ok since we need to check the prefix with CARGO_ of env:
    https://github.com/rust-lang/rust/pull/148559/files#diff-0eaa1095d59f2f3d9c015005d15fd8f7cda13121a8404d77b2955fc5fcd40449R213, and it's a note but not code suggestions, it's maybe incorrect for rare scenarios.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Yeah, seems alright, was just curious to hear what you think.

Comment threadcompiler/rustc_builtin_macros/messages.ftl Outdated
@rust-log-analyzer

This comment has been minimized.

@KivooeoKivooeo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Comment threadcompiler/rustc_builtin_macros/src/env.rs Outdated
Comment threadtests/ui/env-macro/env-cargo-var-typo-issue-148439.rs
Comment threadcompiler/rustc_builtin_macros/src/env.rs
@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@Kivooeo

Copy link
Copy Markdown
Member

@bors r+

@bors

bors commented Nov 6, 2025

Copy link
Copy Markdown
Collaborator

📌 Commit 3edd25f has been approved by Kivooeo

It is now in the queue for this repository.

@borsbors 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 Nov 6, 2025
@jhprattjhpratt mentioned this pull request Nov 7, 2025
bors added a commit that referenced this pull request Nov 7, 2025
Rollup of 12 pull requests
Successful merges:
- #145768 (Offload device)
- #145992 (Stabilize `vec_deque_pop_if`)
- #147416 (Early return if span is from expansion so we dont get empty span and ice later on)
- #147808 (btree: cleanup difference, intersection, is_subset)
- #148520 (style: Use binary literals instead of hex literals in doctests for `highest_one` and `lowest_one`)
- #148559 (Add typo suggestion for a misspelt Cargo environment variable)
- #148567 (Fix incorrect precedence caused by range expression)
- #148570 (Fix mismatched brackets in generated .dir-locals.el)
- #148575 (fix dev guide link in rustc_query_system/dep_graph/README.md)
- #148578 (core docs: add notes about availability of `Atomic*::from_mut_slice`)
- #148603 (Backport 1.91.1 relnotes to main)
- #148609 (Sync str::rsplit_once example with str::split_once)
r? `@ghost`
`@rustbot` modify labels: rollup
@bors
bors merged commit 3186f21 into rust-lang:masterNov 7, 2025
11 checks passed
@rustbotrustbot added this to the 1.93.0 milestone Nov 7, 2025
rust-timer added a commit that referenced this pull request Nov 7, 2025
Rollup merge of #148559 - chenyukang:yukang-fix-148439-env, r=Kivooeo
Add typo suggestion for a misspelt Cargo environment variable
Fixes#148439
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Misleading suggestion when using env!() on a misspelt Cargo environment variable

8 participants

@chenyukang@rustbot@rust-log-analyzer@Kivooeo@bors@Urgau@jieyouxu@fee1-dead