Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: dotnet/linker
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 4b3f78c
Choose a base ref
...
head repository: dotnet/linker
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: c790896
Choose a head ref
  • 5 commits
  • 9 files changed
  • 3 contributors

Commits on Jan 9, 2023

  1. Fix new warning which shows up with latest roslyn (#3179) 

    First encountered in dotnet/runtime#80235, so copying the change to dotnet/linker
    @vitek-karas
    vitek-karas authored Jan 9, 2023
    Configuration menu
    Copy the full SHA
    12885df View commit details
    Browse the repository at this point in the history

Commits on Jan 10, 2023

  1. Update cecil (#3180) 

    To pick up RVA field fix
    @sbomer
    sbomer authored Jan 10, 2023
    Configuration menu
    Copy the full SHA
    7716bee View commit details
    Browse the repository at this point in the history

Commits on Jan 12, 2023

  1. Unpin Microsoft.CodeAnalysis.NetAnalyzers version (#3182)

    @sbomer
    sbomer authored Jan 12, 2023
    Configuration menu
    Copy the full SHA
    10bb5ae View commit details
    Browse the repository at this point in the history

Commits on Jan 14, 2023

  1. Fix race condition in build (#3185)

    @sbomer
    sbomer authored Jan 14, 2023
    Configuration menu
    Copy the full SHA
    4452038 View commit details
    Browse the repository at this point in the history

Commits on Jan 17, 2023

  1. Fix a small bug in message origin for warnings from static field acce… 

    …ss on generic type (#3186)

The warning needs to be generated from the origin where the field reference comes from - so if it's a method body, then from the method body. This is because the instantiation is determined by that place, not the field itself (the field is defined on an open generic definition of the type).

This syncs the relevants tests with a NativeAOT work-in-progress change, but in generately it adds a lot more cases and some better comments.

Co-authored-by: Tlakaelel Axayakatl Ceja <[email protected]>
    @vitek-karas @tlakollo
    vitek-karas and tlakollo authored Jan 17, 2023
    Configuration menu
    Copy the full SHA
    c790896 View commit details
    Browse the repository at this point in the history
Loading