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

error C3611: 'System::Numerics::INumberBase::System::IUtf8SpanFormattable.Try Format': a sealed function cannot have a pure-specifier #94998

Closed
mayadav1 opened this issue Nov 20, 2023 · 5 comments · Fixed by #95018

Comments

@mayadav1
Copy link

Description

I am getting error while building main and release/8.0-staging branch of runtime.
error C3611: 'System::Numerics::INumberBase::System::IUtf8SpanFormattable.Try Format': a sealed function cannot have a pure-specifier

Can somebody help me finding a solution for that.

Reproduction Steps

  1. git clone https://github.com/dotnet/runtime.git -b release/8.0-staging
  2. .\build.cmd clr+libs -c release -a x64

Expected behavior

It should be compiled.

Actual behavior

error C3611: 'System::Numerics::INumberBase::System::IUtf8SpanFormattable.Try Format': a sealed function cannot have a pure-specifier

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Nov 20, 2023
@ghost ghost added the untriaged New issue has not been triaged by the area owner label Nov 20, 2023
@ghost
Copy link

ghost commented Nov 20, 2023

Tagging subscribers to this area: @dotnet/area-system-numerics
See info in area-owners.md if you want to be subscribed.

Issue Details

Description

I am getting error while building main and release/8.0-staging branch of runtime.
error C3611: 'System::Numerics::INumberBase::System::IUtf8SpanFormattable.Try Format': a sealed function cannot have a pure-specifier

Can somebody help me finding a solution for that.

Reproduction Steps

  1. git clone https://github.com/dotnet/runtime.git -b release/8.0-staging
  2. .\build.cmd clr+libs -c release -a x64

Expected behavior

It should be compiled.

Actual behavior

error C3611: 'System::Numerics::INumberBase::System::IUtf8SpanFormattable.Try Format': a sealed function cannot have a pure-specifier

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

Author: mayadav1
Assignees: -
Labels:

area-System.Numerics, untriaged, needs-area-label

Milestone: -

@jkotas jkotas removed the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Nov 20, 2023
@jkotas
Copy link
Member

jkotas commented Nov 20, 2023

@tannergooding Do we need to update the minimum VS version required to build the repo in https://github.com/dotnet/runtime/blob/main/docs/workflow/requirements/windows-requirements.md#visual-studio ?

@tannergooding
Copy link
Member

Do we need to update the minimum VS version required to build the repo in

Probably. Notably, it's not kept up to date as is. New versions of Roslyn only work "correctly" with the latest IDE and so we've already "required" VS 17.8 to work with parts of the codebase for months, but the doc still says 17.3

I'll submit a PR updating that and the C++/CLI tools version

@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Nov 20, 2023
@tannergooding
Copy link
Member

I've put up #95018.

The issue is the same as described in #94723. C++/CLI required a fix to work with a previously unused aspect of Default Interface Members (DIMs). This fix only exists in v14.38 or higher and so VS2022 17.8 or later is required to build those projects currently.

@ghost ghost removed in-pr There is an active PR which will close this issue when it is merged untriaged New issue has not been triaged by the area owner labels Nov 20, 2023
@rzikm
Copy link
Member

rzikm commented Dec 1, 2023

Can we also update the .vsconfig file? or is that unnecessary?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
4 participants