Thread 106588408

For the cniles who moved/decided to learn Rust, why did you do it and how has it worked out?

c wasn't *nile in 2015. it was the right choice. (free)pascal may have been good too if it hadn't already become fringe by then.
rust is now the right choice for new projects.

>rust is now the right choice for new projects
i tried rust for new projects and got filtered
now i use C++ for my new projects rather than C, maybe one day i try C3 for a new project

Got a job, but unfortunately I don't know how to do jackshit. It's in finance and they hired me even though I don't have a degree. They are putting lots of faith that I'll get my shit together, but I'm already focusing on what I can solve, which is backend stuff (the stuff they want me to take is related to crypto ledgers)

I miss traits, iterators and the syntactic sugar of tuples and sumtypes
borrow checking was too much of a pain in the ass though

>>106588669
If u got filtered by Rust then you’d only have it worse with c++

I went from Go to Rust, with a tiny period of using C in between
the type system is fucking great
the generics are very powerful
the ecosystem has a lot of small niche-filling libs, which I prefer over giant ass libs that try and do everything
lazy iteration is useful for composing data manipulation pipelines across different functions (or even libs) while maintaining minimal passes over data
lack of a garbage collector and the borrow checker forces you to write much better data structures that are more machine-friendly. GC is nice, but you must realize that it allows (and even promotes) the use of data structures that are structurally complex. protip: when in doubt, use an arena
the use of traits in the std lib for many small things leads to a very clean design. Rust does not feel like a shoddy language in almost all of its corners and crevices
having native access to sets and b-trees is fucking huge. seriously, both of these data structure types are criminally underused
some downsides:
- the borrow checker is imperfect in that it has false positives
- more traits could have been includes for representing common collection classifications (associationss, sets, etc.)
- the native collections not being able to be backed by custom allocators is such a missed opportunity. in fact, I am in the process of writing my own lib that does this
- needing to use a 3rd party crate (Syn) for AST parsing is stupid
- async closures are scuffed

as for C, dude C is such a fucking archaic ass language it is ridiculous to suggest starting new projects with it. you literally do not even have namespaces. any argument stops there, the end.

>>106589264
>C is such a fucking archaic ass language it is ridiculous to suggest starting new projects with it. you literally do not even have namespaces. any argument stops there, the end.

Just use C++ for the namespaces and write without OOP.

>>106589298
I have zero reason to write C++ when I have Rust. I know several experienced devs (one CTO) that have writteen C++, and they all enjoy Rust now. these are people with 100+ repos

>>106589264
>- more traits could have been includes for representing common collection classifications (associationss, sets, etc.)
do you mean something like the `num` crate for collections?
I don't know if such a thing exists since i never needed it myself. but i can see how it could be useful.
considering home much pressure there was to deliver v1.0 in 2014/2015, it's impressive how much was done, and how much they got right.
>- the native collections not being able to be backed by custom allocators is such a missed opportunity.
that has been the case for years. is your information outdated (llm?), or do you mean something else?
>- needing to use a 3rd party crate (Syn) for AST parsing is stupid
oh, trust me, no one would choose to use rustc's syntax crate for writing proc macros over syn/quote. how would i know? syn didn't always exist ;)

>>106589771
>do you mean something like the `num` crate for collections?
maybe? never used `num`. see Clojure's use of assoc/dissoc across various data structures, conj, etc.

>>106588408 (OP)
I write C++ code for a living and a lot of the restrictions rust places on you would make the codebase much more tolerable and mitigate some of the OOP insanity.

Rust is just a more sane language driven by an actual vision unlike C which refuses to modernise and C++ which just slaps random shit onto it without a guided vision

>>106588408 (OP)
Rust is only really ok if what you're doing is simple and clean data transformations. As soon as you want to do anything complex with a lot of shared state then Rust makes the project much much harder and will force you to use shit like smart pointers en mass, which turns out to be slower than garbage collection. There is a reason Rust's main usecase atm is webdev and that it's pretty much failed in embedded and game dev.

>>106589961
Rust is multi paradigm like c++

>>106590045
In the year of our lord, two thousand twenty five, Rust STILL cannot create structs with dynamically sized fields. C has had this feature since 1999.
When you will you admit having a standards committee force the compilers to implement their vision is superior to github issue RFC chaos where shiny shit gets added and core functionality stays on the backlog forever?

>>106589950
yes. that's what i thought.
num (more specifically num-traits) is a crate that trait-ifies common methods/ops from numeric types, so you can for example do generic clamping or casting. it's almost universally used in the ecosystem.
i didn't come across something similar for collections, probably because there is no big need for it. Vector/Array like types are generalized through slices already. And different maps/sets are not exchangeable with each other usage-wise. and the keys don't even share the same traits bounds. and Hash already provides a generic interface for where hashes are used.

>>106588408 (OP)
Very organic thread, tranny.

>>106589264
>- the native collections not being able to be backed by custom allocators is such a missed opportunity. in fact, I am in the process of writing my own lib that does this
Isn't that just HashMap or something? Vec and Box support allocators as type level arguments.
You can also define your own global allocator.

i love these posts which start while jeets are asleep. because you can pinpoint with accuracy when did they start waking up.

>>106590217
struct Thing {
len: usize,
data: T,
}

fn main() {
let something = Thing { len: 5, data: [0u8; 10] };
let something_else = Thing { len: 10, data: [0u8; 20] };
}

???

>>106590415
Try with a size only known at runtime as in >>106590217.

>>106590438
nigga, you use a Vec or Box<[u8]> (if you don't want the overhead of the capacity)
struct Thing {
len: usize,
data: Box<[u8]>,
}

fn main() {
let something = Thing { len: 5, data: [0u8; 10].into() };
let something_else = Thing { len: 10, data: [0u8; 20].into() };
}

>>106590453
>storing array separately on the heap
>two allocations instead of one
>btfoing cpu cache
I accept your concession.

>>106590453
What you’re doing would be equivalent (according to his code) to uint_8* not uint_8[]

There’s a difference

>>106590217
Just do BYTE[1024*1024] and get it over with

>>106590472
>two allocations
dumb retard

>>106590472
dude, structs are not allocated on the heap, ever
their individual fields might be
you have a fundamental misunderstanding of stack vs. heap
in C, what you are asking for looks like:
typedef struct Thing {
size_t len;
unsigned char *data; /* note the pointer to the heap */
} Thing;

void init(Thing *thing, size_t len) { /* very important to note that *thing points to a value on the STACK */
thing->len = len;
thing->data = malloc(sizeof(unsigned char) * len); /* malloc creates a region on the heap. */
}

int main(void) {
Thing thing; /* there is no malloc call here, so this is on the stack */
init(&thing, 5);
return 0;
}

>>106590499
> structs are not allocated on the heap, ever
Wrong, if you’d need to store structs in say a queue or any ds, then you’d need to dynamically allocate memory for it.

>>106590518
ok yeah you're correct, you can store stacks on the heap by explicitly doing so via the calling of malloc, but I'm trying to explain shit to an obvious noob
I'm done having this argument, it's unironically 1st week systems programming discussion

>>106590531
structs*

>>106590496
>make 10,000
>oom
>>106590497
>>106590499
see >>106590518
Copying stack allocated structs around everywhere isn't free either, and your C code is as spatially wasteful as your Rust is. Too many levels of indirection.

>>106590537
this should be proof that one cannot hate Cniles enough
absolutely disrespectful, pompous ass motherfuckers that think they know everything
if you spoke like this to me IRL I would unironically smack you until my hand and your face got all fucked up

>>106590499
>dude, structs are not allocated on the heap, ever

>>106590554
concession accepted

>>106590537
> Copying stack allocated structs around everywhere isn't free either
As long as you free/delete anything that you allocate, there shouldn’t be any issue, easiest thing ever.

>>106590241
about right on schedule

>>106588408 (OP)
C gets you the work done the easiest way possible, although more responsibility on you as a programmer.

I can’t even declare a global static variable in Rust without having to use { unsafe } blocks or mutex/cell locks

>>106590611
Now, make it static and mut

>>106590665
dumb retard, unsynchronized access to a shared memory location across threads is UB

>>106590665
>noooooo the compiler is preventing me from doing stupid shit
enjoy your test suite being all fucked up with state resets because you are too lazy to pass around state

>>106590594
>global static variable
use case?

>>106590594
how is mutating a global going to be safe without synchronization lol

>>106590683
ok make it single threaded then

>>106590693
Why ru assuming that it needs sync?

>>106590683
Udek what threads are u jeet

>>106590710
safe rust doesn't support global variables like C does
you need not reply anymore

>>106590725
do u even code bro

>>106590537
>Copying stack allocated structs around everywhere
guess the size dumb retard
struct Thing {
len: usize,
arr: Box<[u8]>,
}

impl Thing {
fn new(len: usize) -> Self {
Self { len, arr: vec![0; len].into() }
}
}

fn main() {
let thing = Thing::new(1024);
dbg!(std::mem::size_of_val(&thing));
}

>>106590217
you're asking for
https://en.wikipedia.org/wiki/Flexible_array_member
even C++ does not have this

>>106589264
>the type system is fucking great
low-level c programmer here.
type system?
I basically treat and visualize everything as typeless address space of bytes and sometimes RAX-sized ints.
If I need a constant, and there was an instruction I wrote previously that happened to "be" that constant value (e.g. 0x90 for NOP) then I just set the pointer to that instruction and use that constant.
Oh, sometimes I "see" floats and doubles as types, but that's pretty infrequent.

>>106590967
post code

>>106590967
who asked?

>>106590967
Do you exclusively write device drivers or something?

>>106590967
how many people yell at your for your schizo code

>>106588669
Use Nim instead

>>106590105
>Rust's main usecase atm is webdev and that it's pretty much failed in embedded and game dev
Chat is this true? Has Rust failed?

>>106592083
swap C++ and C and it's true

>>106592092
ok nocoder, tell me more how being filtered by C++ makes you very high IQ lmao
You use C because you're too retarded to understand anything more complex than a plain function call.

>>106592101
genius admires simplicity

>>106592108
template
void
print(Args&&... args) noexcept
{
(print_unchecked(static_cast(args)), ...);
flush();
}

I'd like to see your "genius" and "simple" version of this in C. You have 5 minutes. I'm not going to ask you to implement print_unchecked, simply make this exact syntax compile in C:
print("Cniles tongue my greasy anus ", 24, "hours a day, ", 7, " days a week.\.");

No, you cannot just use printf, because it's complicated garbage unlike what I just wrote.

>>106592122
printf("Sepples tongue my greasy anus %d hours a day, %d days a week.\.", 24, 7);

this is simplicity

>>106592132
>%d
>simplicity
Yeah I'm sure we all are as unemployed as you and have time to memorize arbitrary symbols, oh wait, we don't because we prefer simplicity.

>>106592141
>getting filtered by printf
grim

>>106592141
based retard

>>106592150
printf has to parse a string to figure out what to print, tell us more how that's simpler than just printing things one by one in the order specified by programmer.
>>106592151
Keep your low IQ niggerbabble to yourself.

>>106592132
>>106592150
>>106592151
https://www.cve.org/CVERecord/SearchResults?query=printf

>>106592154
now show the implementation of print_unchecked

>>106592160
void
print_unchecked(char const* const ptr, usize const len) noexcept
{
auto& iov = iovbuf[iovcnt++];
iov.iov_base = const_cast(ptr);
iov.iov_len = len;
}

But let me guess, that's too simple for you, nocoder.

Cniles can't comprehend that function overloading is what leads to simplicity, lmao.
void
print_unchecked(u64 number) noexcept
{
auto const oldptr = reinterpret_cast(numptr);

while (number >= 100)
{
auto const n = (number % 100) * 2;
number /= 100;
numptr -= 2;
__builtin_memcpy(numptr, digits + n, 2);
}

if (number >= 10)
{
auto const n = number * 2;
numptr -= 2;
__builtin_memcpy(numptr, digits + n, 2);
}
else
{
numptr -= 1;
*numptr = '0' + number;
}

print_unchecked(numptr, oldptr - reinterpret_cast(numptr));
}

namespace
{

sys::iovec iovbuf[UIO_MAXIOV];
char numbuf[UIO_MAXIOV * 20];

constexpr char* numbufend = numbuf + sizeof(numbuf);

u32 iovcnt = 0;
char* numptr = numbufend;

constexpr char digits[] =
{
'0','0','0','1','0','2','0','3','0','4','0','5','0','6','0','7','0','8','0','9',
'1','0','1','1','1','2','1','3','1','4','1','5','1','6','1','7','1','8','1','9',
'2','0','2','1','2','2','2','3','2','4','2','5','2','6','2','7','2','8','2','9',
'3','0','3','1','3','2','3','3','3','4','3','5','3','6','3','7','3','8','3','9',
'4','0','4','1','4','2','4','3','4','4','4','5','4','6','4','7','4','8','4','9',
'5','0','5','1','5','2','5','3','5','4','5','5','5','6','5','7','5','8','5','9',
'6','0','6','1','6','2','6','3','6','4','6','5','6','6','6','7','6','8','6','9',
'7','0','7','1','7','2','7','3','7','4','7','5','7','6','7','7','7','8','7','9',
'8','0','8','1','8','2','8','3','8','4','8','5','8','6','8','7','8','8','8','9',
'9','0','9','1','9','2','9','3','9','4','9','5','9','6','9','7','9','8','9','9',
};

}

>0 heap allocations to print text
Way too simple saaaaaaaaaaaaaar, we need printf and heap allocations!

[[gnu::cold]]
void
flush() noexcept
{
auto* iov = iovbuf;

for (;;)
{
i64 written = sys::writev(1, iov, iovcnt);

if unlikely(written <= 0)
{
iovcnt = 0;
break;
}

while likely(iovcnt && iov->iov_len <= written)
{
written -= iov->iov_len;
++iov;
--iovcnt;
}

if likely(iovcnt == 0)
{
break;
}

iov->iov_base = static_cast(iov->iov_base) + written;
iov->iov_len -= written;
}

numptr = numbufend;
}

Show me how much code it would take to recreate this in C... Oh wait, I already made you cry and you can't see the rest through your tears, cniles lmao.

>cnile on cnile violence
lol

namespace sys
{

using iovec = ::iovec;

[[gnu::cold]]
[[nodiscard]]
inline
i64
writev(u32 const fd, iovec const* const iov, u32 const iovcnt)
{
register u64 rax asm("rax") = __NR_writev;
register u32 rdi asm("rdi") = fd;
register iovec const* rsi asm("rsi") = iov;
register u32 rdx asm("rdx") = iovcnt;
asm volatile
(
"syscall"
: "+r" (rax)
: "r" (rdi),
"r" (rsi),
"r" (rdx)
: "rcx",
"r11",
"memory"
);
return rax;
}

}

Well Cnile? Say something.

void
print_unchecked(char const* const ptr, usize const len) noexcept;

template
void
print_unchecked(char const (&ptr)[N]) noexcept
{
print_unchecked(ptr, N - 1);
}

void
print_unchecked(u64 const number) noexcept;

void
flush() noexcept;

template
void
print(Args&&... args) noexcept
{
(print_unchecked(static_cast(args)), ...);
flush();
}

In the end... This is too complex for a Cnile, that's why Cniles are on the left of bell curve, and C++ gods are on the right.

>>106592209
>This is too complex for a Cnile
thanks for admiting that you don't care about simplicity

>>106592218
Tell me which part of this isn't simple.
The 5 minutes to rewrite this in C are over by the way, I accept your concession.

Cniles be like:
#define CALL_EACH(fn, ...) \
_CALL_EACH(fn, __VA_ARGS__ __VA_OPT__(,) _CALL_EACH_END)

#define _CALL_EACH(fn, arg, ...) \
fn(arg) __VA_OPT__(_CALL_EACH_AGAIN _CALL_EACH((fn, __VA_ARGS__)))

#define _CALL_EACH_AGAIN() _CALL_EACH
#define _CALL_EACH_END

>This is simpler and more intuitive than C++ templates

>>106592189
C++ is named correctly, it is a superior language to C, and its users are superior to Cniles. Nobody likes Cniles. C++ was created as a fork of C to prove that it can be improved, and it is still improving daily, while C becomes more and more retarded.
I'd rather write FORTRAN77 than touch a shitty curry language like C.

>>106592275
Saar, please delete this immediately.

>>106592275
>glibc
real simpletons use musl, it's way more simple

>>106592303
How is this simpler than what I posted?
Okay, lets suppose I want to print in binary or hex, I can add two more functions that will be easy to read, e.g. print("pointer = 0x", hex(pointer), "\n"), meanwhile printf is unreadable mess.
Because hex is a struct wrapping the pointer, I can add formatting parameters, IF I NEED THEM.

>>106592329
in C you just add a case to your switch

>>106592343
In C++, there's no switch, because I don't care to overcomplicate shit and waste runtime cycles on something that should be done AOT. Fuck off nocoder, go optimize strlen or something, and remember, in C++ strlen is a no-op.

>>106590217
C had that feature since forever.
typedef struct Thing {
size_t len;
uint8_t data[1];
} Thing;

>>106592371
>>106590217
What's even the usecase of this?
t.
#include
#include

template
class dynamic
{
public:
dynamic(SizeT const len)
{
baseD = new unsigned char[sizeof(SizeT) + len];
*reinterpret_cast(baseD) = len;
}

~dynamic()
{
delete[] baseD;
}

DataT* ptr() const noexcept
{
return reinterpret_cast(baseD + sizeof(SizeT));
}

SizeT len() const noexcept
{
return *reinterpret_cast(baseD);
}
private:
unsigned char* baseD;
};

int main() {
dynamic text{8};
std::memcpy(text.ptr(), "12345678910111213 etc etc", text.len());
text.ptr()[text.len() - 1] = '\0';
std::cout << text.ptr() << '\n';
}

>>106588408 (OP)
No specific reason, I already knew C, came across Rust and learned it for fun, freely available and structured resources on the official Rust website was encouraging.

ITT: bratty cniles correction

>>106588408 (OP)
Bloated language

>>106590217
>no VLAs
meme feature, no one asked for it
meanwhile C has no strings, generics, namespaces or modules in 2025
kys

>>106592896
C++ doesn't have modules either (and modules have no usecase desu)

>>106589170
>If u got filtered by Rust then you’d only have it worse with c++
C++ has a spec.

Since rust people put a fake account of me on github and added feminist shit and a code of conduct to it.

I am going to kill them.
Also I will continue using C, as I have since 2002 or 3

>>106593067
C++ also has a solution for every problem.
Feature bloat is a meme, it's good that there's billion features. There's billion of problems, and C++ solves all.

>>106590554
>this should be proof that one cannot hate Cniles enough
>absolutely disrespectful, pompous ass motherfuckers that think they know everything
>if you spoke like this to me IRL I would unironically smack you until my hand and your face got all fucked up
Since you oppose men marrying cute young virgin girls, a right given by YHWH, I would kill you.

>>106593080
Most of the "features" rust feminists "use" could be done using the most basic C and would run in 1/20th the time.

A good(and "bad") thing about C is that one builds one's development structure with just the routines one needs: and with just what is needed within them.

One can steal source-code from established projects which have already done so if wanted.

This is why C is fast to run.

>>106593080
One can prototype algorithims in PERL to see if one's approach is correct, and then rewrite it in C almost verbatim.

This way you have a "naiieve approach" to check your C code against (which will eventually leave the naiieve approach for something more performat, sometimes machine specific versions).

Can't do that in the insanity that is Rust.

>>106593197
The kind of code I write cannot be prototyped in PERL because I am solving problems more advanced than fizzbuzz.

>>106592915
>modules have no use case
I bet your macros leak as much as your clitty when someone insults C you fucking larping Cnile tranny

>>106593294
>macros
In C++, have no usecase.

>>106593294
geg
cniles try not to recompile a header 50 times after including it 50 times challenge (impossible)
literally no other language has this problem (except c++ and c++ modules suck)

>>106593213
Any mathematical operation can be prototyped in Perl. You're just a anti-child bride faggot.

>>106593382
so show me that AVX512 code in perl

>>106590967
BASED
Kill people that don't like you.

>>106593396
As I said: any mathematical structure can be prototyped in Perl.

It will not be fast. But it will be correct.
And you can check the output against it.

>NOO BUT IT WONT BE RUNNING ON THE ARCHITECTURE !!! IT MUST BE RUNNING ON INTELS AVX512 REGISTERS!!!!
>I CHANGE THE QUESTION TO MAKE ME CORRECT!
It's like you do not know english.
Guess India is awake.

"C is for dalits" that's why you don't like it.
Even though C was invented by whites.
Not indian dogshit like yourself.
You think you're superior because you _use_ some other "better" language.

You can certainly use AVX512 in C.

>>106593486
I don't need correctness, I need speed you retard. Correctness is trivial non-issue. It's implied that code is correct by default, if it wasn't, it would be worthless.

>>106592122
>I'd like to see your "genius" and "simple" version of this in C. You have 5 minutes. I'm not going to ask you to implement print_unchecked, simply make this exact syntax compile in C:
>print("Cniles tongue my greasy anus ", 24, "hours a day, ", 7, " days a week.\.");

print("Cniles tongue my greasy anus ", ftos(24), "hours a day ", ftos(7), " days a week.\.");

> Note: QuakeC :) (but still C)

>>106593502
>>>106593486
>I don't need correctness,
Yes you do.
> I need speed you retard.
You're calling me a retard.
I am going to find you and kill you dead.
My nickname is mikeeusa.
I will permanently remember you.
When I find you or bump into you I will murder you in cold blood.
Do you understand me?
> Correctness is trivial non-issue.
Wrong. It is something you must test for and make unit tests for. Perl is good for this, for algorithims.
First Perl,
then for speed, C.
>It's implied that code is correct by default,
It's implied that young girls are for sex, since they have a pocket to cum in called a pussy, and are cute and nice. Yet white people, like yourself, get it wrong and instead worship a faggot who opposes loli brides.
>if it wasn't, it would be worthless.
Which is why you prototype in Perl,
and then implement a non-naieve approach in C, and then test them against eachother.

I've been programming for longer than you have.
Have some respect.
Or I will kill you.

>>106593502
>I don't need correctness,
Forwarding to your employeer, so as to get you fired so you will be on the street and I can kill you easier.

Since you mentioned AVX512 there aren't too many possibilities.

>>106593594
My code is correct by default, it's not something that I have to put effort into because I'm white and right simply by my existence.

>>106590967
Wow you're such a 1337 hax0r!! I mean x86 has an immediate field for small values while your solution requires indirect addressing and may result in a cache miss while not even decreasing the instruction size but it's so 1337!! Preach to those rusttrannies my c xister!!! They know shit about asm, they don't even force it where it doesn't belong!!

>>106593584
Why would I prototype in Perl when I can do it in C++ because it's a good language unlike C?

>>106593067
>C++ has a spec.
meaningless when (You)r code doesn't follow it.

>>106593594
>doesn't understand logical implication.
what's the point of all these CS 4yr degrees?

>>106593197
>prototype correctness in Perl
>correctness
>in a dynamic language
Jeet moment

>>106593824
None, I don't have a CS degree and I know that code correctness is important, user is always wrong, and performance will be squeezed. Death to shitlangs.

>>106593849
correctness is implied universally, otherwise the software is meaningless. that's the guys point. if you went to school, maybe you'd understand basic logic.

make your own thread, mikee.
nice CoCk btw
https://github.com/MikeeUSA/ChaosEsque-Anthology/blob/main/code-of-conduct.md

>>106593858
I wrote >>106593502
>>106593849 though, just saying that I don't have a CS degree, and I'm proud.

>>106593867
So this... is the power... of pedophile cniles...!!! I kneel

what is it with /g/eets not recognizing a "Story of Mel" inspired larp?
maybe the juniors and sophomores didn't go beyond xkcd yet! very funny "nerdy" comics hehe keke

>>106593867
I DO NOT HAVE A CODE OF CONDUCT.
That github account IS NOT MINE.
My projects were ALWAYS on sourceforge.

>>106593909
What is the problem with that QuakeC?
How would you do it "better"
Why would you do it "better"?

>>106588669
use odin

>>106593824
I have a law degree and a law license.
I simply ignored your assertion that "the code is implied correct". Because it's a bullshit assertion by a anti-child bride white faggot.

>>106593839
>Jeet moment
What colour are my eyes
<----------

>>106594141
then you have no right to comment. this is /g/ - Technology, not whatever retarded shit you think it is. Take your juden career bullshit somewhere else.

>>106593839
>Jeet
What colour are the veins in my wrists
<----------------------------

>>106593197
Here is how Mikee prototypes in perl:
https://github.com/MikeeUSA/GPC-Slots-2/blob/master/gpcslots2.pl#L1141-L1183

>>106594165
>>>106594141(You)
>then you have no right to comment. this is /g/ - Technology, not whatever retarded shit you think it is. Take your juden career bullshit somewhere else.

I'VE BEEN PROGRAMMING SINCE 2001, DIPSHIT. I HAVE A RIGHT TO COMMENT HERE SINCE I ___PREDATE___ YOU DIPSHIT FUCK.

>>106588408 (OP)
You should just use AI instead.

>>106594201
Don't like my code when I was 13 - 17?
Want to fight dipshit?

>>106594216
>Devuan background
>lawyer
oh...... it's Mike E. isn't it? kek, fuck off schizo retard.

>>106594165
>>106593839
>Jeet
What colour are the veins in my wrists
<----------------------------

>>106594231
>oh...... it's Mike E. isn't it? kek, fuck off schizo retard.
I make better opensource projects than you.
I have been programming longer than you.
You never show your code.
You always libel me by linking to a feminist mocku-git-repo that is not mine.

>>106594235
oof, yikes. you look kinda mid. now I know why you want to rape children—adult women don't want to fuck you

>>106594231
>oh...... it's Mike E. isn't it? kek, fuck off schizo retard.
This is NOT YOUR WEBSITE.

>>106594249
You're a tranny fag, and now I know you're a brit too.

YHWH explicitly allows virgin girl children as brides.
We will kill all of you "fellow white people" for denying us brides.
We will adhere to your enemies and open the gates so they may slaughter you and us.

>>106594268
>You're a tranny fag
>We will kill all of you
actually, tranny fags kill you, see charlie kirk.

>>106594201
>white on_$biggirthycockblack

>>106594249
>YIKES a 40 yr old doesn't look like a fucc boy tranny!

I've never had a GF.
There were like 3 girls in highschool that looked good at all. 3 out of a class of 300.

Everyone is fat.
And no I would never "go for" a woman of my age.
I am a virgin. I expect a bride to be a virgin too.
Catholic teaching.

I want a girl child bride as YHWH commands.

>>106594286
charlie kirk opposed child brides.
as do trannies.

Because they are all whites that oppose YHWH"s law.

>>106594294
>Never shows his work
>Mocks others.
Lets see your code from when you were 13-17.

Also my code still works.
Never breaks.
Can you say that about yours 20 years later?

>>106594314
When I was 13-17, I was having sex and partying.

>>106593080
C++ doesn’t have a simple split() kek

>>106593732
The reason is sometimes you need to send out pointer values to constants, like if making a syscall.
Just some examples, there’s a lot more. It’s just a method of work.
Here’s another example. All my jump tables for DFA states are actually just 4 or 8 byte ASCII strings, so I can read them in a memory dump, but treat the string as an int or long for efficiency in actual code. You can also treat those strings as pointers if you set up your memory right (e.g sparsely allocate pages in the vm space at those addresses).

>>106591006
Not exclusively, but they are a mix of C/assembly.
The older C MS compilers are surprisingly good at fluidly mixing asm/C. If you have to interact with COM (ughh) then that’s a C++ layer.

The point is, once you start doing that, you don’t really think in terms if types much any more.

Another benefit is that it is usually somewhat naturally “tamper resistant” if you’re working with licensed code.

>>106594544
splitting a string isn't simple
>>106594649
OOP is a red herring, there's nothing wrong with it besides multiple inheritance trees more inbred than americans who create them.

>>106588408 (OP)
I switched to zig. The best decision I made.
It's the worst of both worlds.
More footgunny than C.
Less safe than rust.
Changes every release.

>>106595155
that choice is horribly not future-proof.
what are you going to do when zig hits v1?

>>106595536
I don't remember how many years ago I got permabanned from main zig repo, but the fact it's still not v1 makes me think that anon will never have to worry about this.

>>106595644
a zigger told me the other month that async was the last item on the agenda. so it should be any year now.

>>106595798
it was last item in 0.7, which version are we on?

Q: Where did the names "C" and "C++" come from?
A: They were grades.

>>106594868
>splitting a string isn't simple
.split() in rust
std::views::split() in C++
Several lines in C, making use of pointers, memcpy and null characters

The choice is obvious.

>>106589170
im using a subset of C++ no one is forcing me to use complex concepts like i was forced to understand in Rust.

>>106596382
my grades were score/max_score
your anglo units are werd

>>106596819
strtok() has been around for decades.
Well known. The standard.
Fast.
Customizable behaviour.
Early exit.
Low memory use.
You can hire someone on fiverr to write an inefficient split in a couple if lines if you’re the type of person that only knows that driving is giving a self-driving electric car voice commands.

>>106596833
That’s the good thing about C++ … it’s mostly a superset of C.
At one point, C had better structure initialization than C++ … not sure if C++ caught up or not, I don’t follow C++ faddish trends anymore.
Name mangling still sucks though when trying to link.

One feature I’d like them to implement in C is lambdas and nested functions, I don’t think those ancient concepts would be incompatible with the spirit of C.

>>106597030
nooooooooooo but if you do multithreded le epic splitter 90000 its bad it modifies global state aaaaaaaaaaaaaaaaaaaa

>>106597105
It’s fine if you know that though.
Also much more efficient. If I want to make a copy vis-a-vis strdup() or on the stack or whatever, I can certainly do that. Iffun i want.

>>106597105
Also, yeah, I used to be fascinated with threads on sun and OS/2 when they came out, but they’re a pain in the ass and I never do it anymore or use OpenMP wher allthe brainthinkings are already inside. 99/100 I split the problem into different processes and minimize communication between them. Do likewise gents.

>>106588408 (OP)
One does not simply learn rust. Rust is a lifestyle. A total tear down and rebuild of the ego. Your life as it existed before will come to an end. Its why there are so many trans rust coders, a complete rebirth fits perfectly with transitioning.

What was once an act of dominance,
has been transformed to an act of submission.

When you must ask, when you must act only towards some woman's wants; on pain of death or capture by the police; enforced at gunpoint, torture prison point; enabled by the sword of damoclese the woman has in her pocket (cellphone).

What was once the top rail, has become the bottom.
Because of White people and their New Testament.

There were previous histories, deleted now; where men did not date women; but raped little virgin girls. That is how they got wives.

Whites are faggots.
And their god Jesus is the enemy of Man.
YHWH is a friend and benefactor of Man.
He made Man the Ba'al.

Which whites condemn as satan.

MARRY LITTLE GIRL VIRGINS.

>>106588408 (OP)
And where are you now?
Do you have a cute little girl bride?

>>106594129
>What is the problem
It's yandere-dev level if-else slop
>How would you do it better
I would have used dynamic dispatch
>Why would you do it better
To make it actually maintainable
>>106594149
>>106594191
>>106594235
White skin, jeet pedophile brain incapable of higher level abstractions. My condolences

>>106597030
strtok doesn't work dumbass.
by splitting they mean
x = "my string"
y, z = x.split(' ') // "my", "string"

ffs. C cuckolds are absolutely retarded.

>>106594249
>YIKES a 40 yr old doesn't look like a fucc boy tranny!

I've never had a GF.
There were like 3 girls in highschool that looked good at all. 3 out of a class of 300.

Everyone is fat.
And no I would never "go for" a woman of my age.
I am a virgin. I expect a bride to be a virgin too.
Catholic teaching.

I want a girl child bride as YHWH commands.

>>106594249
>YIKES a 40 yr old doesn't look like a fucc boy tranny!

I've never had a GF.
There were like 3 girls in highschool that looked good at all. 3 out of a class of 300.

Everyone is fat.
And no I would never "go for" a woman of my age.
I am a virgin. I expect a bride to be a virgin too.
Catholic teaching.

I want a girl child bride as YHWH commands

>>106588408 (OP)
And where are you now?
Do you work?

Do you like doing that?

>>106588408 (OP)
And where are you now?
Do you work?

Do you like doing that?

>>106588408 (OP)
I tried to switch to rust cause I thought tokio and async would be cool. But it’s a freaking dumpster fire so I switched back to C and C++ and it’s a lot better.

>>106597416
>But it’s a freaking dumpster fire
How so?

>>How would you do it better
>I would have used dynamic dispatch
NO YOU WOULD NOT BECAUSE THIS IS QUAKEC AND IT __DOES___NOT___HAVE___THAT.

So again: DIPSHIT: how would YOU have done it.

>>106597352
>>What is the problem
>It's yandere-dev level if-else slop

There's nothing wrong with if-then, dipshit faggot.
EVERYTHING is If-Then, OR lookup tables, OR switch-style offset tables, beyond the syntax.
If you learned any assembly you'd know this.
(it's mostly lookup tables all the way down)

>>Why would you do it better
>To make it actually maintainable
Why would I want transsexuals and feminist "maintaining" my code and the code of other straight men?
Tell me?
Why would I want to make it "easy" for
1) women
2) transsexuals
3) feminists
To fuck with my code and the code of those men who came before me?

>>106597352
>White skin, jeet pedophile brain incapable of higher level abstractions. My condolences
I will kill you, because you oppose men marrying young virgin girls.
Abstraction is of zero value. You're a neophyte faggot white fuck xcoder.
Getting the work done is of value.

Lets see YOUR videogame dipshit fuck?
Lets see YOUR 200+ weapons.
Lets see YOUR city generation
Lets see YOUR building models
Lets see YOUR weapons models.

>>106597425
Much prefer boost or seastar or even straight epoll than rust async have to do pinning and all the crap I have to put up with is objectively bad.

>>106597352
>>How would you do it better
>I would have used dynamic dispatch
>>106597352

Someone tried to write a verbstack in QuakeC once (Nexuiz), it was dog slow.

Whatever you're talking about QuakeC doesn't have: so no you wouldn't.

Tell me dipshit: what datatypes would you use in QuakeC to create your structure for your dynamic thing?

Arrays?
Think again: those don't exist.
They do NOT exist in QuakeC.
>But I saw array like struc...
those are a compiler hack and use 1 global per array element.
So: again: no you wouldn't.
You have a cap of 65k globals.
That's all your fake-array-elements in the program, all your strings, all your _NUMBERS_ (yes x == 1 uses a global)

>>106597474
kek, bullshit. post code of a basic tcp echo server. anyone who says this shit is delusional or literally deranged.

>>106597488
>>106597501
>Faggot rust people reinvent things Quake does in C 30 years ago

>>106597446
>does not have that
Retard, you can implement it trivially in C
>There's nothing wrong with if-then
>EVERYTHING is If-Then
No it's not? Wtf are you even programming since 2001? Bing bing wahoo pedophile mods?
>If you learned any assembly you'd know this
If you learned any assembly you'd have known a long if-else chain with different conditions can't be converted into a jump table by the compiler you dumb fuck. O(n) checks vs O(1) jump
>Lets see YOUR videogame dipshit fuck?
Sure. Here's a screenshot my WebGPU 3D renderer.

>>106597474
>t. probably first person who prefers C++ implementation of async await to Rust async await

>>106597513
>>>does not have that
>Retard, you can implement it trivially in C

We're talking QuakeC here.
So no: you CANNOT implement it in QuakeC.
You were quoting QuakeC code.

So again: asshole: how would you do it in QuakeC.

>>106597513
My Quake based game is better than what you have created.

>>106597513
>>If you learned any assembly you'd know this
>If you learned any assembly you'd have known a long if-else chain with different conditions can't be converted into a jump table by the compiler you dumb fuck. O(n) checks vs O(1) jump

That's why I said, If you would like to read:
>EVERYTHING is If-Then, OR lookup tables, OR switch-style offset tables, beyond the syntax.
See the 3 possiblities?
Do you dipshit faggot?
DO you?

DO YOU FUCKING SEE THE 3 OP-FUCKING-TIONS?
DO YOU FUCKING PIECE OF SHIT?

I've done assembly.
YOU have NOT.

>>106597513
Compiler?
You think I did assembly with a compiler?
Lol.

You think you're better than me.
I am going to kill you and show you that you are not.
This is a direct death threat to you.

>>106597521
do those tards even have their std:: networking library yet?
p sovlless when starting a new C++ project and I'm still fucking with dogshit like libc / unistd C shit.

>>106597378
>I want a girl child bride as YHWH commands
Chapter and verse.

>>106597557
Devarim 22 verse 28
<------------

>>106597557
Deuteronomy 22 verse 28-
And if any should find the
[ child virgin], whoever was not espoused, and
using force on her, he went to bed with her, and he should be found,
[ shall give the man going to bed with her] to the
father of the young woman fifty double-drachmas of silver,
and she will be his wife, because he humbled her;
he will not be able to send her away at any time.

כִּי־יִמְצָא אִישׁ *נַעַר בְתוּלָה אֲשֶׁר לֹא־אֹרָשָׂה
וּתְפָשָׂהּ וְשָׁכַב עִמָּהּ וְנִמְצָאוּ
וְנָתַן הָאִישׁ הַשֹּׁכֵב עִמָּהּ לַאֲבִי *הַנַּעַר
חֲמִשִּׁים כָּסֶף וְלוֹ־תִהְיֶה לְאִשָּׁה תַּחַת אֲשֶׁר עִנָּהּ
לֹא־יוּכַל שַׁלְּחָהּ כָּל־יָמָיו ס

Ἐὰν δέ τις εὕρῃ τὴν παῖδα τὴν παρθένον, ἥτις οὐ μεμνήστευται, καὶ
βιασάμενος κοιμηθῇ μετ᾽ αὐτῆς καὶ εὑρεθῇ,
δώσει ὁ ἄνθρωπος ὁ κοιμηθεὶς μετ᾽ αὐτῆς τῷ πατρὶ τῆς νεάνιδος
πεντήκοντα δίδραχμα ἀργυρίου, καὶ αὐτοῦ ἔσται γυνή, ἀνθ᾽ ὧν
ἐταπείνωσεν αὐτήν· οὐ δυνήσεται ἐξαποστεῖλαι αὐτὴν τὸν ἅπαντα χρόνον.

si invenerit vir puellam virginem quae non habet sponsum et
adprehendens concubuerit cum ea et res ad iudicium venerit
dabit qui dormivit cum ea patri puellae quinquaginta siclos argenti et
habebit eam uxorem quia humiliavit illam non poterit dimittere cunctis
diebus vitae suae

>>106597501
https://github.com/tokio-rs/tokio/blob/master/examples/echo-tcp.rs

here's the Rust version using tokio for instance.

cargo init my-gay-server
cargo add tokio --features full
run that shit.

simple as fuck, no autism, no bullshit.
every single time I deal with any nontrivial C++ "framework" is much more work than this, including the fun of dependency management. also co_* and friends are garbage.

>>106597583
Not in the bible, not commanded by God.

>>106597557
>>>106597378(You)
>>I want a girl child bride as YHWH commands
>Chapter and verse.

No: You will just claim "it doesn't say that".
So I refuse to provide you with chapter and verse.
YHWH's word did not contain "chapter and verse" originally.

>>106597557
I am going to kill you.
Since you do not believe YHWH allows child brides.

>Deuteronomy 22 verse 28-
And if any should find the
[ child virgin], whoever was not espoused, and
using force on her, he went to bed with her, and he should be found,
[ shall give the man going to bed with her] to the
father of the young woman fifty double-drachmas of silver,
and she will be his wife, because he humbled her;
he will not be able to send her away at any time.

כִּי־יִמְצָא אִישׁ *נַעַר בְתוּלָה אֲשֶׁר לֹא־אֹרָשָׂה
וּתְפָשָׂהּ וְשָׁכַב עִמָּהּ וְנִמְצָאוּ
וְנָתַן הָאִישׁ הַשֹּׁכֵב עִמָּהּ לַאֲבִי *הַנַּעַר
חֲמִשִּׁים כָּסֶף וְלוֹ־תִהְיֶה לְאִשָּׁה תַּחַת אֲשֶׁר עִנָּהּ
לֹא־יוּכַל שַׁלְּחָהּ כָּל־יָמָיו ס

Ἐὰν δέ τις εὕρῃ τὴν παῖδα τὴν παρθένον, ἥτις οὐ μεμνήστευται, καὶ
βιασάμενος κοιμηθῇ μετ᾽ αὐτῆς καὶ εὑρεθῇ,
δώσει ὁ ἄνθρωπος ὁ κοιμηθεὶς μετ᾽ αὐτῆς τῷ πατρὶ τῆς νεάνιδος
πεντήκοντα δίδραχμα ἀργυρίου, καὶ αὐτοῦ ἔσται γυνή, ἀνθ᾽ ὧν
ἐταπείνωσεν αὐτήν· οὐ δυνήσεται ἐξαποστεῖλαι αὐτὴν τὸν ἅπαντα χρόνον.

si invenerit vir puellam virginem quae non habet sponsum et
adprehendens concubuerit cum ea et res ad iudicium venerit
dabit qui dormivit cum ea patri puellae quinquaginta siclos argenti et
habebit eam uxorem quia humiliavit illam non poterit dimittere cunctis
diebus vitae suae

>>106597599
So you say that Devarim chapter 22 verse 28 is not in the bible?

>>106597599
You say this is not in the bible:?

And if any should find the
[ child virgin], whoever was not espoused, and
using force on her, he went to bed with her, and he should be found,
[ shall give the man going to bed with her] to the
father of the young woman fifty double-drachmas of silver,
and she will be his wife, because he humbled her;
he will not be able to send her away at any time.

>>106597599
You say this is not in the bible:?
כִּי־יִמְצָא אִישׁ *נַעַר בְתוּלָה אֲשֶׁר לֹא־אֹרָשָׂה
וּתְפָשָׂהּ וְשָׁכַב עִמָּהּ וְנִמְצָאוּ
וְנָתַן הָאִישׁ הַשֹּׁכֵב עִמָּהּ לַאֲבִי *הַנַּעַר
חֲמִשִּׁים כָּסֶף וְלוֹ־תִהְיֶה לְאִשָּׁה תַּחַת אֲשֶׁר עִנָּהּ
לֹא־יוּכַל שַׁלְּחָהּ כָּל־יָמָיו ס

>>106597579
“28. ¶ If a man find a damsel that is a virgin, which is not betrothed, and lay hold on her, and lie with her, and they be found; 29. Then the man that lay with her shall give unto the damsel’s father fifty shekels of silver, and she shall be his wife; because he hath humbled her, he may not put her away all his days.” (Deuteronomy 22:28-29)

No mention or implication of children anywhere.

>>106597599
You say this is not in the bible:?


Ἐὰν δέ τις εὕρῃ τὴν παῖδα τὴν παρθένον, ἥτις οὐ μεμνήστευται, καὶ
βιασάμενος κοιμηθῇ μετ᾽ αὐτῆς καὶ εὑρεθῇ,
δώσει ὁ ἄνθρωπος ὁ κοιμηθεὶς μετ᾽ αὐτῆς τῷ πατρὶ τῆς νεάνιδος
πεντήκοντα δίδραχμα ἀργυρίου, καὶ αὐτοῦ ἔσται γυνή, ἀνθ᾽ ὧν
ἐταπείνωσεν αὐτήν· οὐ δυνήσεται ἐξαποστεῖλαι αὐτὴν τὸν ἅπαντα χρόνον.

>>106597599
You say this is not in the bible:?

si invenerit vir puellam virginem quae non habet sponsum et
adprehendens concubuerit cum ea et res ad iudicium venerit
dabit qui dormivit cum ea patri puellae quinquaginta siclos argenti et
habebit eam uxorem quia humiliavit illam non poterit dimittere cunctis
diebus vitae suae

>>106597619
It's right here:

And if any should find the
[ child virgin], whoever was not espoused, and
using force on her, he went to bed with her, and he should be found,
[ shall give the man going to bed with her] to the
father of the young woman fifty double-drachmas of silver,
and she will be his wife, because he humbled her;
he will not be able to send her away at any time.

>See the word [child virgin]