Skip to content

Add standalone GC out-of-date doc warning #103023

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jun 4, 2024
Merged

Add standalone GC out-of-date doc warning #103023

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/design/features/standalone-gc-loading.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,10 @@ Author: Sean Gillespie (@swgillespie) - 2017
This document aims to provide a specification for how a standalone GC is
to be loaded and what is to happen in the case of version mismatches.

**[Update June 2024] Warning** - The behavior described in this spec for how the CLR interprets environment variables
is out-of-date. See the [public documentation](https://learn.microsoft.com/en-us/dotnet/core/runtime-config/garbage-collector#standalone-gc)
if you want up-to-date instructions on how to configure standalone GC.

## Definitions

Before diving in to the specification, it's useful to precisely define
Expand Down