re-render threads with user handle of reply.
This commit is contained in:
1 parent
1ceb4b1583
commit
f8380db665
515 files changed
+2042
-1496
No files matched your search
+1
-1
@@ -26,7 +26,7 @@ parent_post_id: "1990462184170926463"
|
||||
|
||||
## Branch
|
||||
|
||||
**1/**
|
||||
**1/** @Cheezaight
|
||||
|
||||
@valigo @NOTimothyLottes If this is not Timothy Lottes then who is it?
|
||||
|
||||
|
||||
+2
-2
@@ -26,11 +26,11 @@ parent_post_id: "1990462184170926463"
|
||||
|
||||
## Branch
|
||||
|
||||
**1/**
|
||||
**1/** @mrsteyk1
|
||||
|
||||
@valigo His style goes a bit beyond that, judging by the defines used it’s similar to some form of literate programming but with C preprocessor. And the whole RAM thing iirc was for when he was hot reloading C, he said he later switched to GPU and it’s not exactly required anymore?
|
||||
|
||||
**2/**
|
||||
**2/** @NOTimothyLottes
|
||||
|
||||
@mrsteyk1 @valigo Oh I still use the RAM global struct and pointer even without using CPU side hot reload.
|
||||
|
||||
|
||||
+2
-2
@@ -25,7 +25,7 @@ in_reply_to: ""
|
||||
|
||||
## Thread
|
||||
|
||||
**1/**
|
||||
**1/** @valigo
|
||||
|
||||
People who say "C is modern-day assembly" usually way undershoot it. This guy actually writes C like it's asm:
|
||||
- No types - uints everywhere until a cast to actual type on access.
|
||||
@@ -35,7 +35,7 @@ Is this how all GPU programmers write C?
|
||||

|
||||

|
||||
|
||||
**2/**
|
||||
**2/** @valigo
|
||||
|
||||
This is @NOTimothyLottes btw, with his "Fixing C" talk, it's very cool. I really like mixing up shader code and regular C code in the same file and just ifdefind it out depending on which compiler you runt it through: https://www.youtube.com/watch?v=RrL7121MOeA
|
||||
|
||||
|
||||
+3
-3
@@ -26,15 +26,15 @@ parent_post_id: "1990506460531601538"
|
||||
|
||||
## Branch
|
||||
|
||||
**1/**
|
||||
**1/** @Ron172892111531
|
||||
|
||||
@valigo Wouldn't this make working with arrays more difficult? Array[1] would have to be Array[sizeof(data)] etc
|
||||
|
||||
**2/**
|
||||
**2/** @valigo
|
||||
|
||||
@Ron172892111531 As I said somewhere else, it makes sense sizeof pointer math to be the default. I was just saying that it's confusing because "+1" is not actually "plus one"
|
||||
|
||||
**3/**
|
||||
**3/** @Ron172892111531
|
||||
|
||||
@valigo Ptr+1. It's not plus one byte (or int addition), it's plus one object. I think it's only confusing when people assume pointers are just fancy integers. They're meant to work with arrays, and they do flawlessly as long as one remembers that they are an extension of the array
|
||||
|
||||
|
||||
+1
-1
@@ -26,7 +26,7 @@ parent_post_id: "1990506460531601538"
|
||||
|
||||
## Branch
|
||||
|
||||
**1/**
|
||||
**1/** @TheBonkMaykr
|
||||
|
||||
It is confusing if you aren't used to it, that is true. But if you care about portability, letting the C compiler decide what the size of a pointer is, and how to handle pointer arithmetic, is better long-term.
|
||||
|
||||
|
||||
+2
-2
@@ -26,13 +26,13 @@ parent_post_id: "1990506460531601538"
|
||||
|
||||
## Branch
|
||||
|
||||
**1/**
|
||||
**1/** @attamayte1
|
||||
|
||||
@valigo Pointer arithmetic based on type sizes makes sense when considering aligned load/store memory operations.
|
||||
|
||||
I’d argue that even today, with relaxed rules, we commonly use typed arrays and calculate offsets in bytes only when working with generic buffers, like binary data blobs.
|
||||
|
||||
**2/**
|
||||
**2/** @valigo
|
||||
|
||||
@attamayte1 Yeah it makes sense for it to be the default. It's still confusing :)
|
||||
|
||||
|
||||
+1
-1
@@ -26,7 +26,7 @@ parent_post_id: "1990506460531601538"
|
||||
|
||||
## Branch
|
||||
|
||||
**1/**
|
||||
**1/** @furiouswhopper
|
||||
|
||||
@valigo For real I'm parsing through a binary array and trying to say "the next byte is a uint8_t, the next two bytes are a uint16_t" and the most elegant way to do it is mind-numbingly ugly pointer bullshit.
|
||||
|
||||
|
||||
+1
-1
@@ -26,7 +26,7 @@ parent_post_id: "1990506460531601538"
|
||||
|
||||
## Branch
|
||||
|
||||
**1/**
|
||||
**1/** @mrsteyk1
|
||||
|
||||
@valigo I had the displeasure of being exposed to Hex-Ray’s decompiler for years so I have gotten used to it, but it is annoying ye…
|
||||
|
||||
|
||||
+1
-1
@@ -26,7 +26,7 @@ parent_post_id: "1990506460531601538"
|
||||
|
||||
## Branch
|
||||
|
||||
**1/**
|
||||
**1/** @levs57
|
||||
|
||||
@valigo Interestingly, if you try to write Rust in this way, pointer provenance will cause misoptimizations that break everything.
|
||||
|
||||
|
||||
+4
-4
@@ -25,22 +25,22 @@ in_reply_to: ""
|
||||
|
||||
## Thread
|
||||
|
||||
**1/**
|
||||
**1/** @valigo
|
||||
|
||||
When it comes to pointers, "just use 64 bit integer" is way more intuitive to me. I still remember how confusing it was that "pointer + 1" actually means "+ size_of(type_we_point_to)" when I learned all this stuff. It still kinda messes me up not gonna lie.
|
||||
|
||||
Branches: [[archive/threads/valigo/2025-11-17-when-it-comes-to-pointers-just-use-64-bit-integer/2025-11-18-mrsteyk1-i-had-the-displeasure-of-being-exposed-to-hex]], [[archive/threads/valigo/2025-11-17-when-it-comes-to-pointers-just-use-64-bit-integer/2025-11-18-attamayte1-pointer-arithmetic-based-on-type-sizes-makes]], [[archive/threads/valigo/2025-11-17-when-it-comes-to-pointers-just-use-64-bit-integer/2025-11-18-furiouswhopper-for-real-im-parsing-through-a-binary-array-and]], [[archive/threads/valigo/2025-11-17-when-it-comes-to-pointers-just-use-64-bit-integer/2025-11-18-TheBonkMaykr-it-is-confusing-if-you-arent-used-to-it-that-is]], [[archive/threads/valigo/2025-11-17-when-it-comes-to-pointers-just-use-64-bit-integer/2025-11-18-Ron172892111531-wouldnt-this-make-working-with-arrays-more]], [[archive/threads/valigo/2025-11-17-when-it-comes-to-pointers-just-use-64-bit-integer/2025-11-25-levs57-interestingly-if-you-try-to-write-rust-in-this]]
|
||||
|
||||
**2/**
|
||||
**2/** @onelivesleft
|
||||
|
||||
@valigo Distinct syntax for pointer arithmetic would be good. i.e.
|
||||
ptr += 1; // ptr = ptr + 1;
|
||||
ptr ++= 1; // ptr = ptr + 1 * size_of(type_of(ptr));
|
||||
|
||||
**3/**
|
||||
**3/** @valigo
|
||||
|
||||
@onelivesleft Not sure I agree with specific sign choice but I kinda dig the concept
|
||||
|
||||
**4/**
|
||||
**4/** @onelivesleft
|
||||
|
||||
@valigo Well, you know, only applicable for languages that don't have a ++ :P
|
||||
Reference in new issue
Block a user