Soumen wrote:
Thanks Robert and Brian. We'll revisit migration to 1.41.
Last time we tried 3/4 months back, got some static assertion (if I remember correctly) related to some unsigned and signed comparison coming from archive code. And that time since it's not a must and we didn't have much bandwidth, we left it out. So, just a quick question - was that static assertion due to improper usage of the library or it's some bug in serialization library? If it's due to wrong usage, can you point me to related section of the doc?
any static assertion or warnings are accompanied by notes in the source code where the assertion has been placed. These notes should point to the reasoning behind the assertion. Note that these notes might be a couple of stack frames back from the point where the message was issued. Robert Ramey
Regards, ~ Soumen