philm

Rookie numbers, it's probably 15% on my screen, There's space for a lot more rainbows

"easily" solve it.

FTFY

And we're about to enter the fourth rainbow dimension in the next comment...

We're in the third rainbow, keep building more stripes lol

Depends on what trait bound error messages you have had yet, I had 1000 lines long already, where it's not obvious at all what is meant (and is often a very simple fix). But I'm sure this will get better over time, there's already a bigger ongoing redesign of the type system solver, so maybe it will be integrated into stable rust soon.

but effectively it's bash, I think /bin/sh is a symlink to bash on every system I know of...

Edit: I feel corrected, thanks for the information, all the systems I used, had a symlink to bash. Also it was not intended to recommend using bash functionality when having a shebang !#/bin/sh. As someone other pointed out, recommendation would be #!/usr/bin/env bash, or !#/bin/sh if you know that you're not using bash specific functionality.

That only really works, if the method is self-contained, and written in a language that GPT has seen often (such as python). I stopped using it, because for 1 in 10 successful tries I waste time for the other 9 tries...

This.

If I'm writing something slightly more complex, ChatGPT(4) is mostly failing.

If I'm writing complex code, I don't even get the idea of using ChatGPT, because I'm only getting disappointed, and in the end waste more time trying to "engineer" the prompt, only to get disappointed again.

I currently cannot imagine using ChatGPT for coding, I was excited in the beginning, and it's sometimes useful, but mostly not really for coding...

Yes

Has it though?

AFAIK it has like 4k tokens which roughly translate to 3k words or something like that.

The API has 8k or even 32k (this model should be interesting for something like that, unfortunately still don't have access to it...)

So the docs have to be rather short, that it gets all the relevant stuff, or am I missing something?

I mean yeah, dynamic libraries are great if used correctly (via something like Nix), but the unfortunate truth is, that they are not used correctly most of the time (the majority of the Unix and Windows landscape is just a mess with dynamic libraries).

With modern systems programming (Rust) the disadvantages of static compilation slowly fade away though via e.g. incremental compilation.

That said dynamic libraries are still a lot faster to link and can e.g. be hot-swapped.

Is this a hard error? Like it doesn't compile at all?

Isn't there something like #[allow(unused)] in Rust you can put over the declaration?