What does 'let x = x' do in Rust?
I saw this code in the wild:
fields.sort_by_key(|&(_, ref field)| field.tags().into_iter().min().unwrap());
let fields = fields;
What does the let fields = fields;
line do? Why is it there?
rust
add a comment |
I saw this code in the wild:
fields.sort_by_key(|&(_, ref field)| field.tags().into_iter().min().unwrap());
let fields = fields;
What does the let fields = fields;
line do? Why is it there?
rust
add a comment |
I saw this code in the wild:
fields.sort_by_key(|&(_, ref field)| field.tags().into_iter().min().unwrap());
let fields = fields;
What does the let fields = fields;
line do? Why is it there?
rust
I saw this code in the wild:
fields.sort_by_key(|&(_, ref field)| field.tags().into_iter().min().unwrap());
let fields = fields;
What does the let fields = fields;
line do? Why is it there?
rust
rust
edited 3 hours ago
Shepmaster
153k14301439
153k14301439
asked 3 hours ago
timtheliontimthelion
663919
663919
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
It makes fields
immutable again.
fields
was previously defined as mutable (let mut fields = …;
), to be used with sort_by_key
which sorts in-place and requires the target to be mutable. The author has chosen here to explicitly prevent further mutability.
"Downgrading" a mutable binding to immutable is quite common in Rust.
Another common way to do this is to use a block expression:
let fields = {
let mut fields = …;
fields.sort_by_key(…);
fields
};
add a comment |
The statement let var = var;
makes var
immutable and bound to its current value. fields
was declared as mut
earlier.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54595345%2fwhat-does-let-x-x-do-in-rust%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
It makes fields
immutable again.
fields
was previously defined as mutable (let mut fields = …;
), to be used with sort_by_key
which sorts in-place and requires the target to be mutable. The author has chosen here to explicitly prevent further mutability.
"Downgrading" a mutable binding to immutable is quite common in Rust.
Another common way to do this is to use a block expression:
let fields = {
let mut fields = …;
fields.sort_by_key(…);
fields
};
add a comment |
It makes fields
immutable again.
fields
was previously defined as mutable (let mut fields = …;
), to be used with sort_by_key
which sorts in-place and requires the target to be mutable. The author has chosen here to explicitly prevent further mutability.
"Downgrading" a mutable binding to immutable is quite common in Rust.
Another common way to do this is to use a block expression:
let fields = {
let mut fields = …;
fields.sort_by_key(…);
fields
};
add a comment |
It makes fields
immutable again.
fields
was previously defined as mutable (let mut fields = …;
), to be used with sort_by_key
which sorts in-place and requires the target to be mutable. The author has chosen here to explicitly prevent further mutability.
"Downgrading" a mutable binding to immutable is quite common in Rust.
Another common way to do this is to use a block expression:
let fields = {
let mut fields = …;
fields.sort_by_key(…);
fields
};
It makes fields
immutable again.
fields
was previously defined as mutable (let mut fields = …;
), to be used with sort_by_key
which sorts in-place and requires the target to be mutable. The author has chosen here to explicitly prevent further mutability.
"Downgrading" a mutable binding to immutable is quite common in Rust.
Another common way to do this is to use a block expression:
let fields = {
let mut fields = …;
fields.sort_by_key(…);
fields
};
edited 3 hours ago
answered 3 hours ago
mcartonmcarton
6,43112435
6,43112435
add a comment |
add a comment |
The statement let var = var;
makes var
immutable and bound to its current value. fields
was declared as mut
earlier.
add a comment |
The statement let var = var;
makes var
immutable and bound to its current value. fields
was declared as mut
earlier.
add a comment |
The statement let var = var;
makes var
immutable and bound to its current value. fields
was declared as mut
earlier.
The statement let var = var;
makes var
immutable and bound to its current value. fields
was declared as mut
earlier.
answered 3 hours ago
Govind ParmarGovind Parmar
9,54553257
9,54553257
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54595345%2fwhat-does-let-x-x-do-in-rust%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown