> bug fix: READ-SEQUENCE into displaced arrays with a non-zero offset now writes to the right memory location.
— http://sbcl.org/all-news.html?2.4.8#2.4.8
Uh-oh, surprised I haven't run into that before since I'm like the only Lisp user that regularly uses displayed arrays (which is something I don't understand since they're literally just slices, while everyone else is out here copying into fresh vectors for some reason)
And it's also always good to have some (indirect) C criticism after bashing on Rust
nytpu /
npub13m…hpn79
2024-08-31 01:47:21
Author Public Key
npub13msuj9j46g097smcjp8dzcnzzdgnh9vzkg9448ymgdqxp6fs94hqkhpn79Published at
2024-08-31 01:47:21Event JSON
{
"id": "f5aeb4ea4d77003555e52670d58ea3e369fd70851e0b9977e647aef0567b2f7e",
"pubkey": "8ee1c91655d21e5f4378904ed1626213513b9582b20b5a9c9b434060e9302d6e",
"created_at": 1725068841,
"kind": 1,
"tags": [
[
"proxy",
"https://tilde.zone/users/nytpu/statuses/113054111585536085",
"activitypub"
]
],
"content": "\u003e bug fix: READ-SEQUENCE into displaced arrays with a non-zero offset now writes to the right memory location.\n— http://sbcl.org/all-news.html?2.4.8#2.4.8\n\nUh-oh, surprised I haven't run into that before since I'm like the only Lisp user that regularly uses displayed arrays (which is something I don't understand since they're literally just slices, while everyone else is out here copying into fresh vectors for some reason)\n\nAnd it's also always good to have some (indirect) C criticism after bashing on Rust",
"sig": "e61a6416b9f1d95a6ccf725d9c2e7ac6b3148266d57aa26094b0239292454d10532f2e069b7b83148f7a3f6d36340acc273f4fdd65744ba5a759b891efdf8855"
}