Voit lisätä twiitteihisi sijainnin, esimerkiksi kaupungin tai tarkemman paikan, verkosta ja kolmannen osapuolen sovellusten kautta. Halutessasi voit poistaa twiittisi sijaintihistorian myöhemmin. Lue lisää
@VisualStudio I know some of your devs are all about using emulators as test cases, so can I ask on behalf of us at @mamedev_org why you haven't adopted MAME has a standard test case yet? It's hit C++1x, template, and ICE bugs left and right since late in the VS2017 cycle.
Take, for example, this bug report, which originated from issues compiling MAME: https://developercommunity.visualstudio.com/content/problem/630838/vs2019-v1614-error-with-comparison-operator-in-c-c.html … Or any number of the workarounds visible in our Github history that we've had to implement to maintain MSVC compatibility.
I don't at all intend to detract from projects like @Dolphin_Emu, but it's a little insulting that it's rumored that projects like that are apparently in your standard test suite, yet we've had no end of trouble compiling with MSVC for literally years, and mum's the word.
I'm bordering on a rant here, but especially considering that venerable Microsofties and ex-MSFTies like @aaronsgiles are or have been part of the MAME project, why the reticence?
Thanks for reaching out, Ryan. Let us review this further with our team, and we'll get back to you with our findings
Hi again, Ryan! There is no reticence. We do plan to add new codebases to our real-world code test matrix and MAME could be a good candidate to consider for our next iteration. Thank you also for helping us improve our compiler through the issues you have submitted so far!
That's awesome to hear! For what it's worth, MAME is a pretty brutal test of templates and C++1x support, and it's uncovered bugs in many compilers. I only raised the issue to you good folks, specifically, as it's getting inordinately difficult to remain compilable with MSVC.
Hi Ryan, apologies for these bugs. We're planning to add https://github.com/mamedev/mame to our real-world testing matrix in the next round of refresh, to prevent these kinds of regressions. We have a dev looking at the bug opened on this at developer community
We have a fix for the bug that will be included in a future release. In the meantime, there's a workaround posted at developer community by @starfreakclone, our compiler developer. Please see if that will unblock you.https://developercommunity.visualstudio.com/content/problem/630838/vs2019-v1614-error-with-comparison-operator-in-c-c.html …
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.
