skitter

no profile record

4 か月前議論

Why would it be UB? All objects are behind (thin) pointers, which can be overwritten atomically.

5 か月前議論

I don't understand – what's the point of not collecting mass amounts of personal identity documents and face scans and linking them to online identities?

skitter

8 か月前議論

I do the same in my toy JVM (to implement the reentrant mutex+condition variable that every Java object has), except I've got a rare deadlock somewhere because, as it turns out, writing complicated low level concurrency primitives is kinda hard :p

skitter

10 か月前議論

They're great, compared to cars. But while they have a relatively fast and cheap setup, over the long term light rail and trams are a lot cheaper to run and can coexist with foot & bike traffic easier since the rails make them very predictable.

skitter

10 か月前議論

> for the sole purpose of not having to add them to function signatures all over the place.

I thought it was because you couldn't be fully generic over exceptions.

skitter

2 年前議論

merde_json should also be relatively small.

skitter

3 年前議論

Me likewise – it makes me happy that there's an 800 word article about a pond that used to exist for less than 200 years in my town.

skitter

3 年前議論

That would be great if it was possible, but how do you specify & implement sensible behavior for this:

    void foo(int *a, int b) { a[b] = 1}

At runtime there is no information about whether that write is in bounds and no way to prevent this from corrupting arbitrary data unless you compile for something like CHERI.

skitter

5 年前議論

Afaik for the WebAssembly MVP, the goal was to have a simple, efficient compile target - therefore only integers and floats. To make wasm more useful & easier to integrate, the plan calls for interface types[0], which allow both accessing complex (JS) objects and calling browser APIs.

[0] https://github.com/WebAssembly/interface-types/blob/master/p...

コメント