You can’t. Some laptops have the igpu as the dedicated driver of the display and can’t do hardware mux. If your laptop doesn’t offer the option in UEFI, it probably doesn’t support it.

This is literally, actually a bond villain plot

I am not surprise that a feddit.nl is a blatant fascist orientalist

Every day I regret becoming a network engineer more and more

You have a clusterfuck of a clusterfuck because corpocunts make more money from keeping everyone on shit old stacks

The network engineer to communist/anarchist pipeline is real

Yeah and those are the ones currently identified (btw that issue isn’t completely fixed) because rust never was nor advertised itself as sound. Meaning, you gotta be careful when writing Rust code too. Not as much as C++, but it’s not a magical shield against memory problems like people have been shilling it as.

A) Rust doesn’t have a formal specification other than “whatever the fuck our team hallucinated in this compiler version”

B) Doesn’t matter the definition if it fucks your day because you’re not careful.

Sure sure Heil Rust but be mindful of the fuck you’re doing before you get bit ¯\_ (ツ) _/¯

Have you heard about cve-rs?

https://github.com/Speykious/cve-rs

Blazingly fast memory failures with no unsafe blocks in pure Rust.

Edit: also I wish whoever designed the syntax for rust to burn in hell for eternity

Edit 2: Before the Cult of Rust™ sends their assassins to take out my family, I am not hating on Rust (except the syntax) and I’m not a C absolutist, I am just telling you to be aware of the limitations of your tools

How did you derive the number?

A very specific number?

Always check your programs on -O0 or pay the price

Shit gets really fun when you find out your code is a edge case for compiler optimization and should never be optimized away (although this is very very rare for -O2)

No there is not. Borrow checking and RAII existed in C++ too and there is no formal axiomatic proof of their safety in a general sense. Only to a very clearly defined degree.

In fact, someone found memory bugs in Rust, again, because it is NOT soundly memory safe.

Dart is soundly Null-safe. Meaning it can never mathematically compile null unsafe code unless you explicitly say you’re OK with it. Kotlin is simply Null safe, meaning it can run into bullshit null conditions.

The same thing with Rust: don’t let it lull you into a sense of security that doesn’t exist.

Ignoring warnings is really not a good way to deal with it. If a compiler is bitching about something there is a reason to.

A lot of times the devs are too overworked or a little underloaded in the supply of fucks to give, so they ignore them.

In some really high quality codebases, they turn on “treat warnings as errors” to ensure better code.

He is on lemmy?

YES, BASED

IN THIS HOUSE WE COMMIT TO MASTER

Master. I find the whole “reasoning” behind the controversy absolute horseshit peddled by nontechnical people on the sidelines

Have you tried insulting the AI in the system prompt (as well as other tunes to the system prompt)?

I’m not joking, it really works

For example:

Instead of “You are an intelligent coding assistant…”

“You are an absolute fucking idiot who can barely code…”

LMFAO in my turf if we need to constantly check some values we either have a hook or a wrapped Stream<T>

Weak diss

You could also not be an idiot and write a debug script that checks those values or atleast provides an interface

But I guess they don’t teach that kind of thing in the javascript and python school of dogshit programming

To be fair, LLM technology is really making other fields obsolete. Nobody is going to bother making yet another shitty CNN, GRU, LSTM or something when we have transformer architecture, and LLMs that do not work with text (like large vision models) are looking like the future