social.noyu.me

someone should invent unsigned integers but offset by one

to put you in the festive spirit, here is some german christmas music from sweden https://www.youtube.com/watch?v=2A3kMTZwSQ8

why are there so many feline females in tech? it’s simple folks. you can’t spell catgirl without irc

i set a limit on how many concurrent requests nginx will proxy to GoToSocial, let’s see if that saves my server from certain death the next time marcan replies to me lol

(i deleted the original post i made about this problem and it seems like it took the thread with it? i’m very confused…)

suppose I want to implement a memory allocator, and I want to optimise for simplicity, clarity and ease-of-implementation, rather than being optimally efficient. what is a good strategy? I do need to handle a mix of small and large allocations and freeing needs to work.

#import "Foundation/Foundation.h"

#include <objc/message.h>
#include <objc/runtime.h>

@interface Infinite: NSObject
@end

@implementation Infinite: NSObject
@end

int main(void)
{
    class_addMethod([Infinite self], @selector(loop), objc_msgSend, "@@:");
    [[Infinite new] loop];
    return 0;
}

audiophiles will buy anything, but executable files only import their enumerated list of dynamic libraries

rust question. a common pattern in code i’ve written is:

assert!(foo % bar == 0);
let count = foo / bar;

is there a standard way to do that as a single operation?

one of the things i really like about rust is how it helps you avoid errors by combining an assertion of some assumption (e.g. “foo is not None”) with obtaining a value based on that assumption (e.g. getting the value inside the Some()). so in this case, it’d be really nice if i could do something like foo.div_exact(bar).unwrap(). personally i’d put it in the stdlib…

fuck it, haruhi profile pic time

"dawning realisation" refers to the morning of black friday