• 16 Posts
  • 284 Comments
Joined 1 year ago
Cake day: June 30th, 2025
  • TheMightyCat@ani.socialtoProgrammer Humor@programming.dev•Anon died on the "clang format bad" hill
    31·
    6 days ago

    It was a simplified example.

    B and C can’t share any other attributes without duplication of code

    struct A {
    [[nodiscard]] virtual std::uint32_t DoSomething() = 0;
};

struct B : A {
    std::uint32_t DoSomething() override { 
        return 0;
    }
};

int main() {
    B b;
    b.DoSomething(); //no warning
}

    even if you use virtual attributes aren’t inherited.

    If you ment members instead of attributes this is unrelated to virtual:

    struct A {
    std::uint32_t a;
};


struct B : A {
    void DoSomething() { 
        std::println("B"); 
    }
};

struct C : A {
    void DoSomething() { 
        std::println("C"); 
    }
};

    Now the member is shared and it works fine and there is no virtual.

    There’s also no strict enforcement of inheritance.

    True, but neither is there when just using virtual:

    struct A {
    virtual void DoSomething() = 0;
};

struct B : A {

};

    This compiles fine if final is not added.

    Not that its an issue as reflection has solved this problem:

    consteval std::string_view HasMethods(std::meta::info impl, std::meta::info iface) {
    constexpr auto ctx = std::meta::access_context::unchecked();
    for (auto fn : members_of(iface, ctx)) {
        if (!is_function(fn) || is_special_member_function(fn)) continue;
        bool found = false;
        for (auto cand : members_of(impl, ctx))
            if (is_function(cand) && has_identifier(cand) && identifier_of(cand) == identifier_of(fn) && type_of(cand) == type_of(fn))
                found = true;
        if (!found)
            return std::define_static_string(std::string(identifier_of(impl)) + " is missing " + display_string_of(fn));
    }
    return {};
}


struct A {
    void DoSomething();
};

struct B  {

};
static_assert(HasMethods(^^B, ^^A).empty(), HasMethods(^^B, ^^A));

// g++ -std=c++26 -freflection main.cpp
// main.cpp:30:41: error: static assertion failed: B is missing void A::DoSomething()
// 30 | static_assert(HasMethods(^^B, ^^A).empty(), HasMethods(^^B, ^^A));

    Now you get the strict enforcement of inheritance and no virtual.

  • TheMightyCat@ani.socialtoProgrammer Humor@programming.dev•Anon died on the "clang format bad" hill
    41·
    6 days ago

    Why does it make zero sense in C++?

    edit: simplified example of what i mean

    struct A {
    virtual void DoSomething() = 0;
};

struct B : A {
    void DoSomething() override { 
        std::println("B"); 
    }
};

struct C : A {
    void DoSomething() override { 
        std::println("C"); 
    }
};

void InvokeDoSomething(A* a) {
    a->DoSomething();
}

    vs

    struct B {
    void DoSomething() { 
        std::println("B"); 
    }
};

struct C {
    void DoSomething() { 
        std::println("C"); 
    }
};

template <typename T>
void InvokeDoSomething(T* t) {
    t->DoSomething();
}
  • TheMightyCat@ani.socialtoLinux Phones@lemmy.ca•MAKERphone 2.0 Is an Open, Hackable 4G Phone You Build YourselfEnglish
    10·
    24 days ago

    Has anyone been able to find any info on the modem outside of “A 4G modem for connectivity”

    And how they got it network operator and regulatory approved?

    Which networks and carriers does it work on?

    MAKERphone 2.0 uses 4G LTE Cat-1 with 2G fallback and works with any carrier that gives you a nano-SIM.

    This seems quite vague and while i can’t say for sure but as far as i know you can’t just slot a sim into a modem with any arbitrary IMEI and it works on the long term.

  • TheMightyCat@ani.socialtoLinux Phones@lemmy.ca•What do LineageOS and F-Droid (and possibly other mobile FLOSS) have to say about AI/LLM usage?English
    121·
    25 days ago

    Not sure why you are asking this in a linux phone community but this is the generative AI policy of flathub, pretty much the store for linux phones:

    Generative AI policy

    Submitters must disclose any AI-generated code, documentation, packaging, or other material they know or reasonably believe is included in the application or its Flathub packaging. The disclosure must identify the affected parts and approximate extent.

    Flathub manifests must not contain AI-generated or AI-assisted content. Disclosure does not exempt manifests from this restriction.

    AI used only for research, discussion, or debugging does not need disclosure when no generated material is included in the application or its Flathub packaging. Other disclosed AI-generated material is evaluated at reviewer discretion. Reviewers may reject a submission, including without further review, based on the extent or role of generated material or concerns about its review, quality, or maintainability. Disclosure does not create a presumption of acceptance.

    AI tools or agents must not open or automate Flathub submission pull requests, or generate their commit messages, descriptions, review comments, or replies. Submitters must not request AI-agent reviews.

    Undisclosed or materially misrepresented AI-generated material, or prohibited AI-generated submission or review interactions, may result in rejection. Repeated violations may result in a permanent ban from future submissions and activities.

    https://docs.flathub.org/docs/for-app-authors/requirements#generative-ai-policy

    In general also outside AI specifically the requirements are pretty strict.