Closed notestaff closed 10 months ago
Hey there,
I'll look at this on Wednesday (still on holiday today and tomorrow).
It should only use constexpr vectors if the compiler supports it and our nightlies with glibcxx_debug also work, but they might just not cover your use case.
Do you have a minimal example that fails to compile? I. E., how do you use the alphabet vector?
I can confirm this bug on godbolt with the newest seqan version (it works with seqan 3.2.0): https://godbolt.org/z/fzfTqfdbq
I believe this is a bug in gcc/libstdc++ We can reproduce it here (without seqan): https://godbolt.org/z/oTfhEWrvd
I found this entry on bugzilla, showing at least one person is aware of this issue: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104748
To solve this, we don't guarentee that ""_dna
is constexpr, we could put in another switch, removing the constexpr if -D_GLIBCXX_DEBUG
is set, what do you think @eseiler ?
I suggested following fix: https://github.com/seqan/seqan3/pull/3222
Does this problem persist on the current master?
Is there an existing issue for this?
Current Behavior
Compiling a seqan3-dependent program with -D_GLIBCXX_DEBUG (debug mode) gives errors that don't happen without debug mode:
Expected Behavior
We'd like to compile a seqan3-dependent program under C++20 standard in debug mode, without errors.
Steps To Reproduce
Add -D_GLIBCXX_DEBUG when compiling.
Environment
Anything else?
As always, thanks for your work on seqan!
@eseiler