Now that the dust has settled, why did?

Now that the dust has settled, why did IQfy lie and say that char* is all I need when it can’t even do copy-free slicing?

Tip Your Landlord Shirt $21.68

Black Rifle Cuck Company, Conservative Humor Shirt $21.68

Tip Your Landlord Shirt $21.68

  1. 2 months ago
    sage

    I suppose all of this is supposed to appear organic?

    [...]

    [...]

    [...]

    [...]

    [...]

    0/0/1/2

    • 2 months ago
      Anonymous

      Yes.

    • 2 months ago
      Anonymous

      > posts poster count in first post
      Smartest cnile

  2. 2 months ago
    Anonymous

    Seriously, how many times are you going to post this?

    • 2 months ago
      Anonymous

      Until the char* meme ends.

  3. 2 months ago
    Anonymous

    I deadass though OP was talking about fricking javascript, rust trannies just assume everybody knows their shitty language at a glance when it looks like 5 others.

    • 2 months ago
      Anonymous

      Slices existed 20 years before your braindead cult cnile brainlet.

      • 2 months ago
        Anonymous

        Which way does this behaviour work in c?

        I don't know or care, I haven't touched C in years because I don't do anything that needs memory efficient autism of that level. OP is b***hing about slicing one character at the end of string which is dumb as hell because I'm pretty sure you don't need to do that because C string are always null terminated, but again don't know c

  4. 2 months ago
    Anonymous

    what does this even mean
    help a moron out IQfy bros

    • 2 months ago
      Anonymous

      slicing is cutting up a string or array or whatever to create a new smaller element. Some languages do this by altering the orginal (called a mutation) , others create a copy which can save as a separate variable. Op is b***hing because of this behavior not working the way he wants it too in c

      • 2 months ago
        Anonymous

        ty lots

      • 2 months ago
        Anonymous

        Which way does this behaviour work in c?

        • 2 months ago
          Anonymous

          In C, char* (basically the string primitive of C) is null terminated (ends with a char) instead of length encoded (a field that store the length).
          This is a shitty way of storing strings, because even if you take up less space (3 less bytes), stuff like finding the length is O(n) instead of O(1).
          It also means you can't slice it without making a copy or using a custom struct, which won't be supported by stdlib.
          Length encoding makes zero-copy string operations very easy, since you only need to know where to start in the string and how long the slice is.

          • 2 months ago
            Anonymous

            So keep track of string size and remember to change the size after performing string operations. You act like this is some kind of complex task. It isn't.

          • 2 months ago
            Anonymous

            Okay ill take the bait. C has no concept of strings, standard library and most c libs have just taken the stance that string is null terminated char array. Nobody is preventing you taking a pointer from the char array and only indexing part of it. You seem to be confused what char* actually is. Sure c doesnt have the language level syntastic sugar thta automatically constructs you the struct that contains pointer and length (slicing operation).

          • 2 months ago
            Anonymous

            If your project requires and has the memory to store additional information of structures like strings, you can add that with a simple struct.
            In shit languages you get a bloat way to represent such structures and you have to carry that everyway.
            >basically the string primitive of C
            Also, C doesn't have strings. The primitive type is char.
            If you want your strings to be uint8, char, wchar, or anything else, you have to create that string type.
            char * is a convention by libc
            If you weren't a troony you'd read about the consequences of your bullshit before cutting your dick

            >C has no concept of strings
            Why are you lying? The C standard mentions string 777 (SEVEN HUNDRED AND SEVENTY SEVEN) times.

          • 2 months ago
            Anοnymουs

            If your project requires and has the memory to store additional information of structures like strings, you can add that with a simple struct.
            In shit languages you get a bloat way to represent such structures and you have to carry that everyway.
            >basically the string primitive of C
            Also, C doesn't have strings. The primitive type is char.
            If you want your strings to be uint8, char, wchar, or anything else, you have to create that string type.
            char * is a convention by libc
            If you weren't a troony you'd read about the consequences of your bullshit before cutting your dick

  5. 2 months ago
    Anonymous

    i genuinely cannot tell if this is bait or not

    • 2 months ago
      Anonymous

      Why would this be a bait?

      • 2 months ago
        Anonymous

        because its a very easy thing to do in c?

        • 2 months ago
          Anonymous

          Why are you asking him?

          • 2 months ago
            Anonymous

            because i know the rust vs c shitflinging contest goes hard.

            i wanted to know if it was a moronic rust programmer or some bait post by a c programmer pretending to be a rust programmer.

          • 2 months ago
            Anonymous

            I'll never understand having a team, you rarely get to pick a language that you will work with forever. Even as a principal ypu are limited by the market and what C suite thinks is the best fit.

          • 2 months ago
            Anonymous

            nah i fricking love lua. and anyone we disagrees with me should be beheaded.

            (c is a close second albeit)

          • 2 months ago
            Anonymous

            It is impossible to do with the char* abstraction for strings that c provides.

          • 2 months ago
            Anonymous

            It's not an abstraction, it's the actual raw computation happening on bare metal, that's why it's sharp and pointy, like a piece of metal

          • 2 months ago
            Anonymous

            char* is not a raw computation either. Bare metal only understands logic gates and voltage differentials. Learn how machine works.

  6. 2 months ago
    Anonymous

    >copy free slice
    Who cares? Any slice worth using requires copying. If you are creating a a slice you likely want to operate on it without mutating the original. This means copying generally. If you don't like that this isn't feature in C that's fine, but seems like a small nit pick. Honestly just creating a new array and copying the data from the old string to the new one isn't that bad.

  7. 2 months ago
    Anonymous

    If you think that bad. Just try and create an integer midpoint function

Your email address will not be published. Required fields are marked *