Quantenteilchen

u/Quantenteilchen@discuss.tchncs.de
0 posts · 85 comments

Recent posts

No posts.

Recent comments

Especially since there are a lot of products out now which only list the additives and no actual flavouring on their ingredients. I.e. all the green colour but no taste (since it would have been swamped by other things anyway and is probably sorta expensive?)

on Ich🐮💤🖥️iel · c/ich_iel · 1 pts · 24d

Ui! Was nutzt du für die Farbdefinitionen?

Bzw wie nutzt du diese geteilten Definitionen beim erstellen von automatischen Einstellungsdateien? (Falls du so etwas nutzt.)

More like the difference between a circle with radius r >> 0 vs a point.

It was supposed to be another math pun about a line being 1 dimensional (at least it only requires a single parameter) with a point being 0D and the fact that "deep" conversations could be said to be multi-dimensional.

on The reddit experience · c/reddit · 7 pts · 77d

Right, I did see your name somewhere, but I no longer remember the exact community. Anyway you are now and forever tagged "suddenly: mod" in my client!

I want to hear you say that at one of the conferences/meetings of scientists I could witness live.

Some would tell you "yeah that's obvious, we just need to look in these and those parameter spaces to find out!"

While others would tell you you are blinded by glory or whatever and cannot accept that we do not understand gravity because we think there's mass there but really it's just another correction term.

And some would spin off wildly into other directions...

So yes we have observed an effect and dark matter is a possible solution. But it's not the consensus name for the effect as there are many camps which simply do not need matter (neither dark nor any other kind) as an explanation.

on ich🐧iel · c/ich_iel · 7 pts · 106d

Was? Das Betriebssystem (ist System überhaupt wohlwollendes Zangendeutsch?) welches als erstes auf Fahrer gesetzt hat um äußere Dinge anzusteuern und deshalb auch nur \n braucht kann viele viele Jahre später die meisten äußeren Dinge Dank offener Mindestschnittstellen häufig direkt ansprechen‽

Das ist mir aber neu!

on ich🚂🚃🚃🤓iel · c/ich_iel · 2 pts · 117d

Dafür aktualisiert das viel zu schnell bei den neuen KISS. Vor allem da oftmals gar nicht wirklich kontrolliert wird 😅.

Ich hätte sonst auch noch vermutet, ob es einfache wege zur Gewichtsbestimmung gibt? Denn mega akkurat muss es ja nicht sein um trotzdem nützlich zu sein!

on "AI" audit of rust stdlib · c/rust · 2 pts · 126d

Yes, except rust has even stricter requirements - namely that your struct must only contain the "inherited" field and you still need to tell the rust compiler to use the special #[repr(transparent)]!

This is because the compiler is allowed - under "normal" representation rules - to rearrange basically everything about the memory layout of a struct to better suit its needs. And as far as I know this includes rearranging the location of a field which is arbitrarily deep inside other structures in your struct! As such

struct A {
  foo: u8,
  bar: u8,
}

struct B {
  test: u8,
  nested: A,
}

could theoretically be laid out as bar test foo - as opposed to e.g. foo bar for just A - in memory if the compiler determined that accessing bar at the start of the struct was overall the "best".

If, on the other hand, you use #[repr(c)] you get exactly what you just said, although the direct casting may or may not be undefined still. (I currently do not remember the relevant parts of the nomicon or other treaties I have read about this... I really need to get back into programming rust at some point!)

Quick edit: Expanded the possible memory layout of just the struct A.

on "AI" audit of rust stdlib · c/rust · 2 pts · 127d

Regarding your question about the cast from const* T to UserRef<T>:

This should be legal as long as UserRef<T> is a #[repr(transparent)] wrapper over a const* T and does most of the magic through its implementation.

There are some other requirements iirc, but I am not entirely sure about them and some or all of them should be given here automatically through the architecture and/or a proper smart pointer implementation as a transparent wrapper...

I never thought about it and instantly wanted to reply "wait why can't you do that‽" but now that I thought about it, what would you want the history to look like in that case? A slightly weird rebase? A single commit which seemingly copy pasted the entire other branch with no relation to it left behind?