Skip to content

[0.68] MustBeNoExceptVoidFunctor should depend on the template type parameter to avoid being evaluated too early #9609

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

Merged
merged 4 commits into from
Feb 26, 2022

Conversation

JunielKatarn
Copy link
Contributor

@JunielKatarn JunielKatarn commented Feb 25, 2022

Backport of #9562

Microsoft Reviewers: Open in CodeFlow

asklar and others added 2 commits February 25, 2022 01:21
…r to avoid being evaluated too early (microsoft#9562)

* MustBeNoExceptVoidFunctor should depend on the template type parameter to avoid being evaluated too early

* Change files
Copy link
Member

@vmoroz vmoroz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@JunielKatarn JunielKatarn merged commit 8b72f04 into microsoft:0.68-stable Feb 26, 2022
@JunielKatarn JunielKatarn deleted the 9559-68 branch February 26, 2022 00:57
@tido64
Copy link
Member

tido64 commented Feb 26, 2022

Would it be possible to backport this to 0.66 and 0.67 as well? We're suddenly seeing this issue on CI as well, and we're on 0.66.

@asklar
Copy link
Member

asklar commented Feb 26, 2022

we shouldn't see this on older releases if we are using our own VS image (using vs2019), this should only repro with vs2022. Do you have a link to a failure on vs2019 @tido64 ?

@tido64
Copy link
Member

tido64 commented Feb 27, 2022

You're right, it looks like windows-latest is now using VS2022: https://github.com/microsoft/react-native-test-app/runs/5344100326?check_suite_focus=true

I guess a workaround is to explicitly set windows-2019?

@asklar
Copy link
Member

asklar commented Feb 27, 2022

@tido64 yes, we don't "officially" support vs2022 yet since the project can't yet build with the default toolset that ships in 2022 (v143). One can work around it by installing the v142 toolset in vs2022 (in fact that's what I have on my laptop since 2022 is faster). We have workitems to move to v143 but it will take some time (and requires Office to be able to move too...).

Ideally, you should have CI run the currently-supported config, which is windows-2019.

asklar added a commit to asklar/react-native-windows that referenced this pull request Mar 29, 2022
…arameter to avoid being evaluated too early (microsoft#9609)

* MustBeNoExceptVoidFunctor should depend on the template type parameter to avoid being evaluated too early (microsoft#9562)

* MustBeNoExceptVoidFunctor should depend on the template type parameter to avoid being evaluated too early

* Change files

* Change files

Co-authored-by: Alexander Sklar <asklar@microsoft.com>
asklar added a commit to asklar/react-native-windows that referenced this pull request Mar 29, 2022
ghost pushed a commit that referenced this pull request Mar 31, 2022
…arameter to avoid being evaluated too early (#9749)

* [0.68] MustBeNoExceptVoidFunctor should depend on the template type parameter to avoid being evaluated too early (#9609)

* MustBeNoExceptVoidFunctor should depend on the template type parameter to avoid being evaluated too early (#9562)

* MustBeNoExceptVoidFunctor should depend on the template type parameter to avoid being evaluated too early

* Change files

* Change files

Co-authored-by: Alexander Sklar <asklar@microsoft.com>

* Change files

Co-authored-by: Julio César Rocha <JunielKatarn@users.noreply.github.com>
ghost pushed a commit that referenced this pull request Mar 31, 2022
…arameter to avoid being evaluated too early (#9750)

* MustBeNoExceptVoidFunctor should depend on the template type parameter to avoid being evaluated too early (#9609)

* Change files
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants