Skip to content
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

Nullness issue - Async.SwitchToContext lacks a null annotation on its parameter #18055

Closed
1 of 7 tasks
glchapman opened this issue Nov 24, 2024 · 3 comments · Fixed by #18059
Closed
1 of 7 tasks

Nullness issue - Async.SwitchToContext lacks a null annotation on its parameter #18055

glchapman opened this issue Nov 24, 2024 · 3 comments · Fixed by #18059
Labels
Area-Nullness Issues related to handling of Nullable Reference Types Bug good first issue help wanted
Milestone

Comments

@glchapman
Copy link

Issue description

I believe that Async.SwitchToContext should take a parameter of type System.Threading.SynchronizationContext | null. Examining the function body, you can see that it treats null as a possible argument and handles it normally (without throwing an exception).

Choose one or more from the following categories of impact

  • Unexpected nullness warning (false positive in nullness checking, code uses --checknulls and langversion:preview).
  • Missing nullness warning in a case which can produce nulls (false negative, code uses --checknulls and langversion:preview).
  • Breaking change related to older null constructs in code not using the checknulls switch.
  • Breaking change related to generic code and explicit type constraints (null, not null).
  • Type inference issue (i.e. code worked without type annotations before, and applying the --checknulls enforces type annotations).
  • C#/F# interop issue related to nullness metadata.
  • Other (none of the categories above apply).

Operating System

Windows (Default)

What .NET runtime/SDK kind are you seeing the issue on

.NET SDK (.NET Core, .NET 5+)

.NET Runtime/SDK version

net9.0

Reproducible code snippet and actual behavior

No response

Possible workarounds

One can write a wrapper function which when given null calls Async.SwitchToThreadPool, otherwise calls SwitchToContext with the non-null syncContext.

@T-Gro
Copy link
Member

T-Gro commented Nov 25, 2024

You are correct, thank you for spotting this.

The annotation at

static member SwitchToContext : syncContext:System.Threading.SynchronizationContext -> Async<unit>
must be adjusted, the doc comment is already correct.

@T-Gro T-Gro removed their assignment Nov 25, 2024
@BoundedChenn31
Copy link
Contributor

Looks like this annotation and all compiler directives at CreateSwitchToAsync can be removed? It is called only by SwitchToContext that checks context for null and PostWithTrampoline definitely doesn't handle nulls well.

#if BUILDING_WITH_LKG || NO_NULLCHECKING_LIB_SUPPORT
let CreateSwitchToAsync (syncCtxt: SynchronizationContext) =
#else
let CreateSwitchToAsync (syncCtxt: SynchronizationContext | null) =
#endif
MakeAsyncWithCancelCheck(fun ctxt -> ctxt.PostWithTrampoline syncCtxt ctxt.cont)

@T-Gro
Copy link
Member

T-Gro commented Nov 25, 2024

CreateSwitchToAsync is not part of the public surface (IIRC). If it is not called with a potentially null value anywhere in FSharp.Core, it can be made strict indeed .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Nullness Issues related to handling of Nullable Reference Types Bug good first issue help wanted
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants