Question Does anybody have recently so much issues with Visual Studio 2019?

[YuliApp]

Intelisense not working often, lot of display bugs, connection issues to FTP. Since two updates ago. Before it all worked fine

 

[Schmide]

Yeah. Apparently you need to build your own defenses.

These are mine for one project.

#pragma warning( disable : 4244 )
#pragma warning( disable : 4305 )
#pragma warning( disable : 4334 )
#pragma warning( disable : 4838 )
#pragma warning( disable : 26451 )
#pragma warning( disable : 6297 )

Stop telling me my shifts may overflow, no one shifts near or past 32bits.

64 bit decided the default operand would be 32 bits, if I add a 32bit value to a 64 bit value just extend it, don't make me explicitly cast it to shut up intelisense ...

I feel better now...

 

[YuliApp]

still having serious issues with intelisense, compiler and such :-( it used to be so stable and reliable :-(

 

[Schmide]

I will admit it did make me do some things better but it's like 100 alarms in a space capsule.

I had this code

    __m256i reindexTable;
    if (deindexTable) {
        Reindexer(reinterpret_cast<short int *>(&reindexTable), indexTable, deindexTable, 16);
    } else {
        reindexTable = *reinterpret_cast<__m256i *>(indexTable);
    }

and intelisense wouldn't shut up about variable being unset because it can't see past the reinterpret_cast.

It did lead to a better solution, though technically it should produce the same code.

    union {
        short int reindexTable[16];
        __m256i reindexTableVect;
    };
    if (deindexTable) {
        Reindexer( reindexTable, indexTable, deindexTable, 16);
    } else {
        reindexTableVect = *reinterpret_cast<__m256i *>(indexTable);
    }

 

[YuliApp]

C++ is whole another mess of compiler issues. I was so happy what they did with C#/VB but now is getting really bad. Since it started there has been like 4 updates of 1 GB and is still the same :-(

 

[YuliApp]

I will admit it did make me do some things better but it's like 100 alarms in a space capsule.

I had this code

    __m256i reindexTable;
    if (deindexTable) {
        Reindexer(reinterpret_cast<short int *>(&reindexTable), indexTable, deindexTable, 16);
    } else {
        reindexTable = *reinterpret_cast<__m256i *>(indexTable);
    }

and intelisense wouldn't shut up about variable being unset because it can't see past the reinterpret_cast.

It did lead to a better solution, though technically it should produce the same code.

    union {
        short int reindexTable[16];
        __m256i reindexTableVect;
    };
    if (deindexTable) {
        Reindexer( reindexTable, indexTable, deindexTable, 16);
    } else {
        reindexTableVect = *reinterpret_cast<__m256i *>(indexTable);
    }

i like the "before" code more.