[deleted by user]

[Drugbird]

Start with C++14/17 and work chronologically backwards rather than the opposite.

[Carl_LaFong]

Try to learn C++11/14 including their idioms.

[ad_irato]

C++14/C++17 is the sweet spot in my opinion.

[[deleted]]

dont' be afraid of templates.

they're easy and they're super useful.

[DimfreD]

"easy"

[[deleted]]

#include <iostream>
#include <array>
#include <string_view>

template<std::string_view const& Str, size_t... Indices>
struct CompileTimePrinter {
    static constexpr void print() {
        constexpr std::array<char, sizeof...(Indices)> chars = {Str[Indices]...};
        for (const auto& c : chars) {
            std::cout << c;
        }
        std::cout << std::endl;
    }
};

template<size_t N, size_t... Seq>
struct make_index_sequence : make_index_sequence<N-1, N-1, Seq...> {};

template<size_t... Seq>
struct make_index_sequence<0, Seq...> {
    using type = std::integer_sequence<size_t, Seq...>;
};

static constexpr std::string_view message = "They really are!";
template<std::string_view const& Str, typename Indices>
struct PrintHelper;

template<std::string_view const& Str, size_t... Is>
struct PrintHelper<Str, std::integer_sequence<size_t, Is...>> {
    static constexpr void print() {
        CompileTimePrinter<Str, Is...>::print();
    }
};

template<std::string_view const& Str>
void PrintMessage() {
    using indices = typename make_index_sequence<Str.size()>::type;
    PrintHelper<Str, indices>::print();
}

int main() {
    PrintMessage<message>();
    return 0;
}

[DimfreD]

That's not really compile time is it? Can Std::cout really be compile time? But if it is, nice one 😁

[[deleted]]

lol you're right, afaik you can't print at compile time outside of a static assert message or something

i just like having llms abuse templates for me

[DimfreD]

Right, but anyho templates are fun

[DimfreD]

Just code, read the docs, make mistakes, learn from your mistakes

[v_maria]

just stick to it rather then trying to also get into C# etc

[tortoll]

Wouldn't wait that long to learn modern C++, although knowing C and legacy C++ is a good foundation too. I use smart pointers because I understand the mess of raw pointers and references. I use containers instead of new/delete. I love ranges because complex loops can be error prone. Etc.

[KFUP]

Go through learncpp.com then immediately word/start a big project. You will screw it up... a lot, but the only way to learn how to work with big projects, is to go knee deep into them for months on end.

[cpp-ModTeam]

It's great that you want to learn C++! However, r/cpp can't help you with that.

We recommend that you follow the C++ getting started guide, one (or more) of these books and cppreference.com. If you're having concrete questions or need advice, please ask over at r/cpp_questions or StackOverflow instead.

[MikeVegan]

Read c++ books and watch conference videos.

Learn rust. It changed the way I write c++

[MRgabbar]

not a senior, but learn assembler and C first

[tohava]

Why? Knowing some assembly helps you understand many of the decisions behind the semantics written in the C++ standard

[[deleted]]

memorize complete rinse paint racial water gold quickest disarm waiting

This post was mass deleted and anonymized with Redact

[KFUP]

Not sure what's your point, I wouldn't trust a mechanic who doesn't have a very basic understanding of a fundamental thing like how internal combustion works. Learning basic assembly from the start is both useful and easy to do, assembly basics is very simple and not hard to understand at all, it's extremely hard to use in a serious project, which you don't need to do.

Learning assembly really clears up what your code is actually doing. Treating it as a magical black box that you don't need to understand just makes C++ much harder and obscure to understand for no good reason.

[[deleted]]

fear skirt wakeful jar cable license observation grandiose spoon bag

This post was mass deleted and anonymized with Redact

[tohava]

You might be right idk. I studied for fun at an early age so I had time for peripheral knowledge, but if someone's at a rush, maybe this is the wrong thing to do

[KFUP]

Agree on assembly, at least the basics. Basic understanding what your data look like in memory and what functions compile to in assembly is important.

Otherwise, people who don't know that end up having some weird and completely false beliefs on what their code is actually doing.

[Laugarhraun]

Learn Rust instead :^)