Closures (C#)
-
I love closures and lambdas, but I was quite amused when I wrote the following buggy code:
for (int i=0; i <= 10; i++)
{
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(i);
... other stuff
});
}And was wondering, how in the world does
iget equal to 11!!! :laugh: Answer: bad closure. Fix:for (int i=0; i <= 10; i++)
{
int n = i;
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(n);
... other stuff
});
}I think this would make a good interview question!
Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkMarc Clifton wrote:
I think this would make a good interview question!
And I thought this was fairly common knowledge! :laugh: (Not that that would preclude it from being an interview question, of course.) They "fixed" the behaviour for the
foreachloop back in C# 5, but deliberately chose not to change theforloop:Closing over the loop variable considered harmful, part one | Fabulous adventures in coding[^]:
UPDATE: We are taking the breaking change. In C# 5, the loop variable of a
foreachwill be logically inside the loop, and therefore closures will close over a fresh copy of the variable each time. Theforloop will not be changed.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
I love closures and lambdas, but I was quite amused when I wrote the following buggy code:
for (int i=0; i <= 10; i++)
{
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(i);
... other stuff
});
}And was wondering, how in the world does
iget equal to 11!!! :laugh: Answer: bad closure. Fix:for (int i=0; i <= 10; i++)
{
int n = i;
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(n);
... other stuff
});
}I think this would make a good interview question!
Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity Framework -
Marc Clifton wrote:
I think this would make a good interview question!
And I thought this was fairly common knowledge! :laugh: (Not that that would preclude it from being an interview question, of course.) They "fixed" the behaviour for the
foreachloop back in C# 5, but deliberately chose not to change theforloop:Closing over the loop variable considered harmful, part one | Fabulous adventures in coding[^]:
UPDATE: We are taking the breaking change. In C# 5, the loop variable of a
foreachwill be logically inside the loop, and therefore closures will close over a fresh copy of the variable each time. Theforloop will not be changed.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
That's the follow-up interview question. "On what
forloops does closure work?"Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity Framework -
I love closures and lambdas, but I was quite amused when I wrote the following buggy code:
for (int i=0; i <= 10; i++)
{
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(i);
... other stuff
});
}And was wondering, how in the world does
iget equal to 11!!! :laugh: Answer: bad closure. Fix:for (int i=0; i <= 10; i++)
{
int n = i;
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(n);
... other stuff
});
}I think this would make a good interview question!
Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkReminded me of The Deadlock Empire[^]. A game where you're a scheduler and have to break code by switching contexts :D You can play it for free in your browser, no registration or anything.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
I love closures and lambdas, but I was quite amused when I wrote the following buggy code:
for (int i=0; i <= 10; i++)
{
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(i);
... other stuff
});
}And was wondering, how in the world does
iget equal to 11!!! :laugh: Answer: bad closure. Fix:for (int i=0; i <= 10; i++)
{
int n = i;
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(n);
... other stuff
});
}I think this would make a good interview question!
Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity Framework -
I love closures and lambdas, but I was quite amused when I wrote the following buggy code:
for (int i=0; i <= 10; i++)
{
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(i);
... other stuff
});
}And was wondering, how in the world does
iget equal to 11!!! :laugh: Answer: bad closure. Fix:for (int i=0; i <= 10; i++)
{
int n = i;
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(n);
... other stuff
});
}I think this would make a good interview question!
Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkMarc Clifton wrote:
I think this would make a good interview question!
To mention the language that shall not be named (it rhymes with GuavaScript), closures was one of the ways to fake OOP before es6 came along with classes.
function FakeClass() {
// analogous to a protected variable
const protectMe = 'When I grow up, I wanna be a class!';// with an anonymous function (kinda like a method)this.doSomething = function() {
// "protectMe" will exist after this function is called
console.log(protectMe);
}
}const sup = new FakeClass();
console.log(sup.protectMe); // not defined
sup.doSomething(); // prints "When I grow up, I wanna be a class!"These days I tend to use closures less and less with generators, promises, async/await, etc. There are just new ways to do the same thing in the language that shall not name be named. But, if you ever find yourself needing to access that lexical context after the parent function go bye bye (a static variable wouldn't quite cut it for that) and you don't want to clutter up your code with global/module crap... closures are a life saver. All-in-all, cool stuff.
Jeremy Falcon
-
I love closures and lambdas, but I was quite amused when I wrote the following buggy code:
for (int i=0; i <= 10; i++)
{
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(i);
... other stuff
});
}And was wondering, how in the world does
iget equal to 11!!! :laugh: Answer: bad closure. Fix:for (int i=0; i <= 10; i++)
{
int n = i;
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(n);
... other stuff
});
}I think this would make a good interview question!
Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkThat is why Java will only let you use _final_ “variables” for anonymous inner classes. Does StartTestConvert() receive by value/copy or by reference? ( Does it matter?) I would tend to wrap some of this into a class. I have moved in the direction of hiding threads/locks/async/await etc as much as possible from the client code. new Runner(i).launch();
-
Marc Clifton wrote:
I think this would make a good interview question!
To mention the language that shall not be named (it rhymes with GuavaScript), closures was one of the ways to fake OOP before es6 came along with classes.
function FakeClass() {
// analogous to a protected variable
const protectMe = 'When I grow up, I wanna be a class!';// with an anonymous function (kinda like a method)this.doSomething = function() {
// "protectMe" will exist after this function is called
console.log(protectMe);
}
}const sup = new FakeClass();
console.log(sup.protectMe); // not defined
sup.doSomething(); // prints "When I grow up, I wanna be a class!"These days I tend to use closures less and less with generators, promises, async/await, etc. There are just new ways to do the same thing in the language that shall not name be named. But, if you ever find yourself needing to access that lexical context after the parent function go bye bye (a static variable wouldn't quite cut it for that) and you don't want to clutter up your code with global/module crap... closures are a life saver. All-in-all, cool stuff.
Jeremy Falcon
lambdas/closures are used in "Lisp, C#, C++, Lua, Python, Ruby, JavaScript, Java, Excel or Google sheets" according to stack overflow, hence my unfamiliarity, being a lowly C guy. Thanx to CP, I have a new appreciation.
"A little time, a little trouble, your better day" Badfinger
-
Marc Clifton wrote:
I think this would make a good interview question!
To mention the language that shall not be named (it rhymes with GuavaScript), closures was one of the ways to fake OOP before es6 came along with classes.
function FakeClass() {
// analogous to a protected variable
const protectMe = 'When I grow up, I wanna be a class!';// with an anonymous function (kinda like a method)this.doSomething = function() {
// "protectMe" will exist after this function is called
console.log(protectMe);
}
}const sup = new FakeClass();
console.log(sup.protectMe); // not defined
sup.doSomething(); // prints "When I grow up, I wanna be a class!"These days I tend to use closures less and less with generators, promises, async/await, etc. There are just new ways to do the same thing in the language that shall not name be named. But, if you ever find yourself needing to access that lexical context after the parent function go bye bye (a static variable wouldn't quite cut it for that) and you don't want to clutter up your code with global/module crap... closures are a life saver. All-in-all, cool stuff.
Jeremy Falcon
-
Marc Clifton wrote:
I think this would make a good interview question!
To mention the language that shall not be named (it rhymes with GuavaScript), closures was one of the ways to fake OOP before es6 came along with classes.
function FakeClass() {
// analogous to a protected variable
const protectMe = 'When I grow up, I wanna be a class!';// with an anonymous function (kinda like a method)this.doSomething = function() {
// "protectMe" will exist after this function is called
console.log(protectMe);
}
}const sup = new FakeClass();
console.log(sup.protectMe); // not defined
sup.doSomething(); // prints "When I grow up, I wanna be a class!"These days I tend to use closures less and less with generators, promises, async/await, etc. There are just new ways to do the same thing in the language that shall not name be named. But, if you ever find yourself needing to access that lexical context after the parent function go bye bye (a static variable wouldn't quite cut it for that) and you don't want to clutter up your code with global/module crap... closures are a life saver. All-in-all, cool stuff.
Jeremy Falcon
I thought you were kidding, but it actually exists :laugh: [GitHub - MaxwellWilliams/guavascript: CMSI 488 Compilers repository for Evan and Max's group project.](https://github.com/MaxwellWilliams/guavascript)
-
lambdas/closures are used in "Lisp, C#, C++, Lua, Python, Ruby, JavaScript, Java, Excel or Google sheets" according to stack overflow, hence my unfamiliarity, being a lowly C guy. Thanx to CP, I have a new appreciation.
"A little time, a little trouble, your better day" Badfinger
C’s still an awesome language. Always will be. Can’t hurt to learn a second one though to be introduced to modern concepts. Some you can bring back to C, even if you have to implement them yourself. Either way, C rulez yo.
Jeremy Falcon
-
You’re welcome man. You can actually do even more with closures too. Might type up some other examples tomorrow.
Jeremy Falcon
-
I love closures and lambdas, but I was quite amused when I wrote the following buggy code:
for (int i=0; i <= 10; i++)
{
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(i);
... other stuff
});
}And was wondering, how in the world does
iget equal to 11!!! :laugh: Answer: bad closure. Fix:for (int i=0; i <= 10; i++)
{
int n = i;
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(n);
... other stuff
});
}I think this would make a good interview question!
Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity Frameworkint n = i;
Amazing solution from an amazing language to cut the code clutter delivered to you by the Cool Kids on the Codeblock!
-
I love closures and lambdas, but I was quite amused when I wrote the following buggy code:
for (int i=0; i <= 10; i++)
{
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(i);
... other stuff
});
}And was wondering, how in the world does
iget equal to 11!!! :laugh: Answer: bad closure. Fix:for (int i=0; i <= 10; i++)
{
int n = i;
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(n);
... other stuff
});
}I think this would make a good interview question!
Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkFrom the good, old K&R C bible: A for that does not include a continue: for (e1; e2; e3) Block; is equivalent to: e1; while(e2) { Block; e3; } Replace e1 with (int i = 0;) and it will become clear what is the scope of i, and why it will have value 11. All subsequent languages like C++, java, C# etc. follows the same logic, since nobody dares to change what DMR (may God rest his soul in peace) has ruled.
-
I love closures and lambdas, but I was quite amused when I wrote the following buggy code:
for (int i=0; i <= 10; i++)
{
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(i);
... other stuff
});
}And was wondering, how in the world does
iget equal to 11!!! :laugh: Answer: bad closure. Fix:for (int i=0; i <= 10; i++)
{
int n = i;
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(n);
... other stuff
});
}I think this would make a good interview question!
Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkChatGPT explained this to me. I feel bad that I couldn't figure this one out :( Question to ChatGPT:
In this example c# code "i" can equal 11. can you fix it?
for (int i=0; i <= 10; i++)
{
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(i);
... other stuff
});
}Response:
Yes, in the provided code, the variable i is captured by the async lambda expression, which means by the time the async operations inside the lambda complete, the value of i may have changed. To fix this, you need to capture the loop variable correctly. Here's a way to do it:
for (int i = 0; i <= 10; i++)
{
int current = i; // Capture the current value of i
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(current);
// ... other stuff
});
}By capturing the loop variable inside the loop, you ensure that each async operation receives its own copy of the loop variable, preventing the issue where the value of i changes before the async operation completes.
-
ChatGPT explained this to me. I feel bad that I couldn't figure this one out :( Question to ChatGPT:
In this example c# code "i" can equal 11. can you fix it?
for (int i=0; i <= 10; i++)
{
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(i);
... other stuff
});
}Response:
Yes, in the provided code, the variable i is captured by the async lambda expression, which means by the time the async operations inside the lambda complete, the value of i may have changed. To fix this, you need to capture the loop variable correctly. Here's a way to do it:
for (int i = 0; i <= 10; i++)
{
int current = i; // Capture the current value of i
var task = Task.Run(async () =>
{
var convertResp = await StartTestConvert(current);
// ... other stuff
});
}By capturing the loop variable inside the loop, you ensure that each async operation receives its own copy of the loop variable, preventing the issue where the value of i changes before the async operation completes.
I just had a conversation with ChatGPT about the topic. It was interesting that I was asking it questions about some specifics about what it was explaining and it did not fall over into a "I'm sorry, 2 plus 2 does equal 5" type of conversation. That has happened a lot to me in the past when trying to understand something.
-
I do not see the difference whether using i or n. Is async call creating a thread? Is this a C# thing? lambda? Closure? seems like a definition of global and local variable spaces. Confused
"A little time, a little trouble, your better day" Badfinger
It has to do with capture, where we grab the value of
iby the use of assignment intonbefore launching another task. There is nothing magical about using a variable namedn... we could have called itgeorge. What's important is that the current value ofiin theforloop is captured before launching the task. If we had not done that, the for loop would complete execution, settingito 11 before the first task was launched. That is what is meant by closure.
