Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)L
Posts
439
Comments
601
Joined
3 yr. ago

  • You can always find a new shitshow

    Having to deal with different volumes and types of shit can be a very welcomed move. Perfect is the enemy of good.

  • If it’s not constant at you may get the loop invariant movement. But only if the compiler can tell that it’s invariant.

    The point is that if the predicate is evaluated at runtime then the compiler plays no role because there is no compile-time constant and all code paths are deemed possible.

    I suppose what I should have said is more like “in many cases you won’t see any performance difference because the compiler will do that for you anyway.”

    I understand that you're trying to say that compilers can leverage compile-time constants to infer if code paths are dead code or not.

    That's just a corner case though. Your compiler has no say on what code paths are dead if you're evaluating a predicate from, say, the response of a HTTP request. It doesn't make sense to expect this hypothetical scenario to be realistic when you have no info on where a predicate is coming from.

  • My advice: use descriptive variable names.

    The article is really not about naming conventions.

  • Ive been paying attention which is why I dont see the communities youre talking about (especially after ive tweaked things).

    You're not paying any attention to what your bot is doing if you aren't noticing where and what your bot is posting.

    If you want it removed from c++ node and cloud I can do that (I assume you do considering what youve been saying so will remove the three communities from the bots sight)

    That does not fix the problem you're creating.

    The problem is that your bot is dumping spam onto Lemmy, and apparently you don't even realize how broken your bot is.

    If I wanted to ban your bot from the communities I moderate, I would already have done so. That does not fix the problem though.

    I don't see how it's reasonable to expect that your misjudgement in deploying a broken bot should be solved by forcing others to cleanup after you, or do extra maintenance work just to avoid the mess you're creating.

    In the very least, your bot should be opt-in, and it should directly cross-post stuff onto the communities that want a bot to generate traffic for them instead of annoying people.

    Lastly, if you want additional evidence that your bot is broken by design, here's the absurd suggestion it posted onto !gamedev@programming.dev triggered by a post with a Godot example.

    Do you really believe you're doing anyone any favor by suggesting to post a Godot C# sample to communities dedicated to the C programming language and .NET?

  • I don’t believe you have to specify the condition at compile time. I think that optimization would fall under dead code elimination.

    How do you tell if some code behind a conditional is dead if the predicate that drives the condition is evaluated at runtime?

  • which communities?

    If you're paying any attention to what your bot is doing, you'll be aware of which communities it's triggering and what/how many messages it's spamming them with.

    Nevertheless, again: the problem with your bot is that it's broken by design. If your goal is to cross-post submissions to related communities, instead of spamming discussions with requests your bot would be cross-posting submissions to related communities. If you did any semblance of requirements gathering, you would also notice that a basic feature of these bots is a) be opt-in, b) stop posting based on community feedback.

  • I’m reasonably sure compilers can shift the if out. I believe it’s called “loop invariant code motion”.

    That scenario would only apply if the condition was constant and specified at compile time. There's no indication on whether var1 or var2 are compile-time constants or predicates evaluated at runtime.

  • for node.js it seems like it was triggering (...)

    The problem is not how the bot is triggered. The problem is that the bot is broken by design. Its main output is spamming Lemmy instances with posts that add no value at all.

    I mean, haven't you even noticed that in some communities your bot is posting more messages than the number of daily visitors?

    What exactly do you plan to achieve with this?

    Please shut down your bot.

  • The article on c/programming was about postgresql and the article on c/postgresql was about performance.

    It really doesn't matter. It's really not about the article. It's about the high volume of spam that you are trying to generate on programming.dev communities without creating any value at all. I mean, your bot is not cross-posting content: it's spamming communities to get someone else to do the work.

    Here's the latest screwup that your bot is creating (link):

    The !nodejs@programming.dev community currently lists 3 active users per month, and your bot spammed it on each new post sent to it asking those 3 active users to cross-post stuff to multiple communities. This is nuts.

    Again, please stop with all the spamming. Your bot is the single most damaging thing done to programming.dev since its been launched.

  • Leaving my 0.02$ here:

    Please don't deploy this bot. It's annoying, it contributes nothing to actually create interesting content for the community to engage, and in fact its main output is spam.

    It does more harm than good. Please don't.

    I'd add that if the idea was any good then instead of spamming people left and right, it would suffice to crosspost stuff on target communities.

  • It's an interesting little gotcha, but I wonder if it wouldn't be preferable to just implement a type trait like is_expensive_conversion that is false by default and true for specific cases, and just static_assert this stuff.

    Relying on obscure implicit type conversion mechanics for this feature feels like being too clever for your own good.

  • Thanks for the info. Interesting.

  • Even then, you’ll still want to have in mind instances known for spam, bots, or shady content have been blocked.

    Is there a list tracking these instances?

  • C++ @programming.dev

    Qt 6.5.3 Released

    www.qt.io /blog/qt-6.5.3-released
  • Python @programming.dev

    Python 3.12 Preview: Static Typing Improvements

    realpython.com /python312-typing/
  • C++ @programming.dev

    Build reliable and secure C++ programs

    learn.microsoft.com /en-us/cpp/code-quality/build-reliable-secure-programs
  • C Programming Language @programming.dev

    A gentle introduction to static analyzers for C (16 Sep 2023)

    nrk.neocities.org /articles/c-static-analyzers
  • Cloud @programming.dev

    Kafka As An Antipattern

    joshaustin.tech /blog/kafka-as-an-antipattern/
  • Cloud @programming.dev

    Introducing the Nuvem subsea cable | Google Cloud Blog

    cloud.google.com /blog/products/infrastructure/introducing-the-nuvem-subsea-cable/
  • C++ @programming.dev

    Inside STL: The deque, implementation - The Old New Thing

    devblogs.microsoft.com /oldnewthing/20230810-00/
  • Cloud @programming.dev

    11 Principles for building and scaling feature flag systems

    docs.getunleash.io /topics/feature-flags/feature-flag-best-practices
  • Cloud @programming.dev

    Data Contract Specification

    datacontract.com
  • Programming @programming.dev

    Most UI Applications are Broken Real-time Applications

    thelig.ht /ui-apps-are-broken/
  • Programming @programming.dev

    SQLite: Database File Format

    www.sqlite.org /fileformat2.html
  • C++ @programming.dev

    In-depth: Functional programming in C++ (2012)

    www.gamedeveloper.com /programming/in-depth-functional-programming-in-c-
  • Cloud @programming.dev

    Getting Used To Microservices

    two-wrongs.com /getting-used-to-microservices.html
  • Node.js @programming.dev

    Bringing forward the End-of-Life Date for Node.js 16

    nodejs.org /en/blog/announcements/nodejs16-eol
  • Node.js @programming.dev

    Welcome to Node.js

  • C++ @programming.dev

    C++Builder: Community Edition - Embarcadero

    www.embarcadero.com /products/cbuilder/starter
  • Cloud @programming.dev

    Metastable failures in the wild

    muratbuffalo.blogspot.com /2023/09/metastable-failures-in-wild.html
  • Cloud @programming.dev

    Death by a thousand microservices

    renegadeotter.com /2023/09/10/death-by-a-thousand-microservices.html
  • C++ @programming.dev

    Formatting Text in C++: The Old and The New Ways

    mariusbancila.ro /blog/2023/09/12/formatting-text-in-c-the-old-and-the-new-ways/
  • C++ @programming.dev

    Using final in C++ to improve performance (2022)

    blog.feabhas.com /2022/11/using-final-in-c-to-improve-performance/