msvc has a candidate fix in Visual Studio 2019 version 16.10 Preview 2. impressively quick turnaround. https://t.co/g39hGvp5ky
gcc has ack'd the codegen problem
#cpp#cpp20
Three compilers, three different results. https://t.co/zq5jivmex4
Bugs filed for msvc and gcc after .@zygoloid clarification: https://t.co/lNfkS5d583
msvc gets it right without the auto param with an explicit template pack expansion. icc/edg, clang, & msvc agree
#cpp20#cpp
@ChrisWooldridge@mattgodbolt@Usborne Zaks wrote a lot on the topic, but I had a hard time liking the Z80 with its nonorthogonal I/O as a wee kid. The lack of beauty horrified me :P I grew up with 6502, 68000, PDP-11 assembler before eventually relenting to the 8088 dark-side. Stuck to BASIC on CP/M machines
Three compilers, three different results. https://t.co/zq5jivmex4
Bugs filed for msvc and gcc after .@zygoloid clarification: https://t.co/lNfkS5d583
msvc gets it right without the auto param with an explicit template pack expansion. icc/edg, clang, & msvc agree
#cpp20#cpp
@experquisite@AlgoTrdr@JoeSaluzzi AFAIK Nomura at JPX (nee TSE) were the first I know of to do this. ~2.3us back then which is v slow by today's standards
@AlgoTrdr@JoeSaluzzi Mostly. Just a TCP header would likely be an ill formed pkt unless the ex supports IP fragments - some do - most don't. Sending two pkts each with a tcp header to form a complete ord message depending on the ord msg header component may help. OOO TCP - tail first - can also work
@experquisite@PaulWestmontUsa@AlgoTrdr@JoeSaluzzi Pkt invalidation used to be hidden as most ex's didn't monitor data link layer errors, but some ex's now get annoyed by this due to better logging. FIFO ts determinism lowers ord jitter => inbound latency more critical & pkt fragments create complexity & possible errs