ThePhD on Nostr: An important separator in what makes a good array abstraction from an awful one is ...
An important separator in what makes a good array abstraction from an awful one is whether your compiler understands it at a native level or not.
Right now, C and C++ don't really cut the mustard there. I wonder if I can improve that situation for C, at the very least...
Published at
2025-04-17 15:36:25Event JSON
{
"id": "0e0c5027005b6bd9c46b86dde897c3e8f4a24808791295bfdb880cc18a460f09",
"pubkey": "2845572814e3205908fd23768b14285a03b693513bfb9b7087435924b04bc19e",
"created_at": 1744904185,
"kind": 1,
"tags": [
[
"proxy",
"https://pony.social/users/thephd/statuses/114354040709832561",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.mostr.pub"
]
],
"content": "An important separator in what makes a good array abstraction from an awful one is whether your compiler understands it at a native level or not.\n\nRight now, C and C++ don't really cut the mustard there. I wonder if I can improve that situation for C, at the very least...",
"sig": "0dca02e7fdb67ecaa9dddba8de18515f29e8c3f629be285b389b262c4ea125d8736daf9c8cf47632e64d5629c0a7b8d97f61bbd2abbf9729203797b12a8d1d2d"
}