Once Seqan 2.x is integrated it will still produce lots of compiler warnings. Their team welcome pull requests to silence them (but not for the 1.x series).
This is slightly less bad now that I've hidden the seqan usage behind an opaque pointer in 6a93d766009ba0f3bf7a5c7e58d0c490b3064450. Now the headers are only parsed once during the build. Still noisy but much less so.
Once Seqan 2.x is integrated it will still produce lots of compiler warnings. Their team welcome pull requests to silence them (but not for the 1.x series).
https://github.com/seqan/seqan/issues/710#issuecomment-75767916