The Wayback Machine - https://web.archive.org/web/20201012101947/https://github.com/topics/garbage-collector
Skip to content
#

garbage-collector

Here are 101 public repositories matching this topic...

marek-safar
marek-safar commented Jul 30, 2019

We can build much smaller Mono runtime for .NET Core purposes by simply removing code we don't need in this configuration. We did a few easy initial steps but we can go much further.

This list is not comprehensive but parts like

  • Culture Data
  • Any PAL related code
  • Unused icalls
kdnilsen
kdnilsen commented Oct 7, 2020

The version and build number should be written to standard output with the reporting of other configuration information.

Adding this information to the output helps make comparison of results between different runs more meaningful and helps assure repeatability of test results. (In theory, it may not be meaningful to compare results from version N with results from version N+1.)

itssamuelrowe
itssamuelrowe commented May 13, 2020

The compiler should analyze the function body to detect statements that are completely unreachable because of return and throw statements that cause a function to exit.

Consider the following example:

function main(...arguments)
    return 0
    print('Hello, world!')

In the above example, the print statement is never executed because main() is terminated before it can reach t

Improve this page

Add a description, image, and links to the garbage-collector topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the garbage-collector topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.