Use C++ 17 about nimskull HOT 5 CLOSED

C++ backend is on the flaky side. We don't even know what are its expectations and what is the generator design.

I'd say changes to it will be on very low priority.

from nimskull.

I see two issues enumerated and it's impossible to know how many issues will be introduced. I think we have to ignore the backends until they are the weak link; garbage in, garbage out, right.

Though I admit that I do wish the cpp backend worked more often, and I'm curious if this could help CPS's C++ codegen issues. 😬

from nimskull.

I see two issues enumerated and it's impossible to know how many issues will be introduced. I think we have to ignore the backends until they are the weak link; garbage in, garbage out, right.

I totally agree that this is very low priority and I've got no interest in supporting knock on effects. Guess that means that the near term mission needs further clarification.

from nimskull.

@xflywind can you reread the readme to see what's the mission right now and based on your understanding do one of the following:

• start a discussion asking to expand the scope and how you'll support that expansion
• open an issue, asking to clarify the near term mission, along with your current interpretation

I'd like to avoid doing this issue by issue stuff, as that's painful for everyone, and at the same time want to make sure you're heard and vice versa.

from nimskull.

Fair enough. The alternative way is nim-lang/Nim#18836 to workaround one of the issues.

from nimskull.