Move to C++17 ? #34

New issue

Closed

opened 2024-03-25 14:54:02 +01:00 by williamjcm · 2 comments

williamjcm commented

2024-03-25 14:54:02 +01:00

Owner

As much as it pains me, I'm thinking about bumping the C++ standard from C++14 to C++17 solely so I can do this:

namespace Foo::Bar {
    // stuff goes here
}

TODO:

Evaluate the impact on compile times, in both debug and release configurations.

As much as it pains me, I'm thinking about bumping the C++ standard from C++14 to C++17 solely so I can do this: ```cpp namespace Foo::Bar { // stuff goes here } ``` TODO: - [ ] Evaluate the impact on compile times, in both debug and release configurations.

williamjcm added the

question

label 2024-03-25 14:54:02 +01:00

williamjcm self-assigned this 2024-03-25 14:54:02 +01:00

williamjcm added this to the v1.5.0 milestone 2024-07-14 14:42:52 +02:00

williamjcm added reference one-point-five

2024-07-14 14:42:55 +02:00

williamjcm removed the

question

label 2024-07-14 14:43:08 +02:00

williamjcm commented

2024-07-14 14:44:09 +02:00

Author

Owner

Removing the question tag and setting the milestone to 1.5.0. It's gonna be needed.

Well, it's technically avoidable, but I'd rather not deal with raw unions, so...

Removing the question tag and setting the milestone to 1.5.0. It's gonna be needed. Well, it's *technically* avoidable, but I'd rather not deal with raw unions, so...

williamjcm referenced this issue

2024-07-14 14:50:29 +02:00

0.11 save reading issues #37

williamjcm added a new dependency 2024-07-14 14:50:52 +02:00

#37 0.11 save reading issues

williamjcm commented

2024-07-14 19:34:41 +02:00

Author

Owner

Done in 53c58ba979.

Done in 53c58ba97932cba3e4f00ec3d819c72587a54edc.

williamjcm closed this issue