-
Notifications
You must be signed in to change notification settings - Fork 784
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 and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS3511 warning when using for...in
in task CE with .NET SDK 6.0.400 in Release builds
#13657
Comments
Might be worth checking if this fixed in VS and VS4Mac 17.3 as I think there was a fix a similar code generation BUG see #13415 ? |
I encountered the exact same issue a few days ago, but it only shows up when I build in Release mode. Tried today building against dotnet |
No, I pretty sure it's a different issue. But that fix might've caused it to break in .400. |
for...in
in task CE with .NET SDK 6.0.400for...in
in task CE with .NET SDK 6.0.400 in Release builds
Correct about only in Release mode. I’m not sure how I wrote the whole bug report and didn’t explicitly state that but included the |
We have several functions with |
13415 is totally separate issue of this.
As Tim said this issue is not related to 6.0.400 and happened also before. |
I'm closing as a duplicate of this: #12038 |
I'm also seeing this crop up in CI, whereas it wasn't there previously (for the same code). As the OP describes, this specifically happens when using
@TimLariviere said this happened in 6.0.303. @sasmithjr said in the OP that this did not happen with 6.0.302. There's no inconsistency; the behavior seems to have been introduced in 6.0.303.
|
Sorry I didn't see that this got closed and couldn't follow up.
So that is an issue and it is the issue that I presented in my original comment, but it's actually not the issue I encountered in my actual codebase lol when I was trying to recreate a smaller version of the problem to reproduce it for this issue, I accidentally reproduced the top level issue and assumed it was the warning I was bumping in to in my codebase. In my production code base, tasks (in functions in modules) with It seems @cmeeren called out a warning with tuples in this comment. I'm not sure if it's the exact same issue, and I'm not sure if it's being explicitly tracked, though. Want me to update this main comment in this issue for better tracking? Or don't worry about it? |
In the latest SDK (6.0.400), I'm receiving a FS3511 warning with
for...in
loops intask
when building for Release. This warning wasn't present in previous SDKs (e.g. 6.0.302)Repro steps
dotnet build -c Release
Can repro with https://github.com/sasmithjr/FS3511-repro-for..in
Expected behavior
Builds without warning
Actual behavior
Receive the warning
warning FS3511: This state machine is not statically compilable. A resumable code invocation at '(2,4--2,8)' could not be reduced. An alternative dynamic implementation will be used, which may be slower. Consider adjusting your code to ensure this state machine is statically compilable, or else suppress this warning.
Known workarounds
Suppressing the warning or using collection
iter
functions.Related information
Thanks for the help, and please let me know if I can provide anymore info.
The text was updated successfully, but these errors were encountered: