I just came. Yup, you read that correctly, I was masturbating to your post. Just wanted to let you know.

I like the c++ one because its obvious whats happening in there. Compare the rust code you don't really know what is created/destroyed. Still it should not make much of a difference for the compiler I assume but that probably depends on what objects you are handling.

fn main() {
    let text = String::from("python rules sepples drools");

    let words: Vec<String> = text
        .split_whitespace()
        .map(|s| s.to_string())
        .collect();

    for word in words {
        println!("{}", word);
    }
}

>>107643894
kek AI bot caught hook line and sinker

>>107643894

shouldn’t you use Vec<&str> there instead? It’d save heap allocations iirc

>>107643952
>>107643918
its from copilot no idea how rust works just wanted a example thats not c++

>>107643894
>Compare the rust code you don't really know what is created/destroyed
It allocates at these function calls only:
>String::from()
>to_string()
>collect()
The point of every one of these functions is to convert to an owned type, so most Rust programmers hopefully understand that they allocate.
Rust doesn't typically do any heap allocation without an explicit function call. C++ does it all the time thanks to its constructors.
All of them are actually superfluous AI slop. You can leave them out for a more concise version that doesn't allocate:

fn main() {
    let text = "python rules sepples drools";

    let words = text.split_whitespace();

    for word in words {
        println!("{}", word);
    }
}

or just:

fn main() {
    let text = "python rules sepples drools";

    for word in text.split_whitespace() {
        println!("{}", word);
    }
}

This would be the C++ equivalent (though a bit less smart about whitespace):

#include <print>
#include <string_view>
#include <ranges>

int main () {
    std::string_view text = "python rules sepples drools";

    for (auto word : text | std::views::split(' ')) {
        std::println("{}", std::string_view(word));
    }
}

in haskell this is just

main = do
  let text = "python rules sepples drools"
  mapM_ putStrLn (words text)

>>107644191

i was wondering if you could do with no allocations, thanks for showing an example, i was too tired to open docs

>>107644191
>code autism
fuck security
fuck open source
fuck the new world order

>>107644288
why did you click on the code autism thread

>>107644261
>>107644191
That still allocates and under high memory pressure that code will fail.

>>107644338
For the I/O or anywhere else?

>>107643844
>used #include instead of import
>whined about verbosity but won’t import Vector, String, InputStringStream and other classes into scope
wow almost like you deliberately made c++ look unpalatable

>>107644191
it is not 1999 anymore retard

import std;

using std::string_view;
using std::views::split;

int main () {
    string_view text = "python rules sepples drools";

    for (auto word : text | split(' ')) {
        std::println("{}", string_view(word));
    }
}

>>107644384
I actually tried import std but couldn't find a compiler that implemented it. Can you post a godbolt link?

PYTHONSAR

>>107644395
Try Clang 18+ and GCC 15+. They apparently support modules.
https://arewemodulesyet.org/tools/

>>107644544
Still doesn't work in Godbolt. Or locally with Clang 19:

split.cpp:1:8: fatal error: module 'std' not found
    1 | import std;
      | ~~~~~~~^~~
1 error generated.

Maybe more tooling would fix it but I'm not gonna install and configure a third-party build system just to use the standard library in this 10-line example program, sorry.

nocoder here those arent even remotely close to being equivalent