>> - MSVC: <=2010, 2012, 2013, 2015, >=2017, none Since 2019 Final is as-good-as-out (Preview has been out for a while), I'd suggest adding it to the list: - MSVC: <=2010, 2012, 2013, 2015, 2017, >=2019, none
>> What would you like the most: Perhaps add an item related to moving to newer C++ standards, something like "- More rapid dropping of older compilers/C++ standards in favour of more slick Eigen codebase & newer C++ features support" (This is really too things - the first one being of particular interest to Eigen developers/contributors. As Michael mentioned in the other thread, it might induce more contributions if the code base got rid of old cruft). -Patrik On Thu, 28 Feb 2019 at 19:41, Gael Guennebaud <[email protected]> wrote: > Thank you for the initiative. Following the previous discussion, I would > suggest something like that: > > C++ version > - today: 03, 11, 14, 17 > - likely in 2021: 03, 11, 14, 17, 20 > > Compiler > - MSVC: <=2010, 2012, 2013, 2015, >=2017, none > - GCC: <=4.8,4.9,5,6,7,>=8, none > - clang: <=4, 5, 6, >=7, none > - ICC: <=16, 17, 18, >=19, none > - XCode: <=8, 9, >=10, none > - others: text-field > > What would you like the most: > - More frequent releases > - More & faster bug fixes > - Speed improvements > - More features, name one: text-field > > > > Arch (check boxes): x86-64, ARM, CUDA, HIP, SYCL, MIPS, Altivec, VSX, > ZVector > > > > On Thu, Feb 21, 2019 at 5:54 PM David Tellenbach < > [email protected]> wrote: > >> Hello together, >> >> as discussed in another mail thread, this mail thread tries to gather >> questions that are suitable for a little survey among Eigen users and >> developers to find out how and with which tools Eigen is currently used and >> how and with which tools Eigen will be used in the future. >> >> I think focussing on simple checkbox questions or questions that can be >> answered in one or two sentences is a good idea. >> >> Cheers, >> David >> >>
