Also notifications.
All my notifications are groups these days.
255 karma · joined June 2, 2012
All my notifications are groups these days.
Llvm won't use it for anything. (I think it starts putting things at 8). Trying to access it explicitly in C will generate `unreachable` instructions.
Last I checked it was only in a mesa dev version. But it would be a standard hopefully everyone using Vulkan can support
a * b;
Is either: a times b if a is a var, or declare a varible b with type a. If a is a typedef.
Also:
some_type b = {a, b, c, d};
Is only valid if some_type is an array or a struct. Which is possibly defined elsewhere in the source.
(I tend to see this syntax in some code bases (some_type) { a, b, c, d }, which is a bit better).
Is that what was happening. It just felt like scroll was spazzing out. Usually I was just trying to push a button near the top of the screen.
Edit: Servo has rust bindings for it, so they might also be using it.
SIGBUS is simialr to SIGSEGV (It happens if a mmap is larger that the backing file and you try to read the unbacked memory). You basically have to handle it if you don't control the backing file, Eg: with shared memory when the other process resizes it after you've mmap'd it. libwayland-server can install one for you that replaces the map with 0'd memory.
One difference here is there a lot of JS developers available to hire an much fewer Qt or even C++ devs.
Although I'm pretty sure you can overload the Fn* traits to implement currying in Rust. (Fn traits are unstable). Which is neat.
// Something like this:
impl<F, A, B, R> (FnOnce(A) -> Curry<F, A, B>) for F
where F: FnOnce(A, B) -> R,
{ ... }
// and
impl<F, A, B, R> (FnOnce(B) -> R) for Curry<F, A, B>
where F: FnOnce(A, B) -> R
What happens in rust closures have a unique type[1]. So the recursive call in cps_factorial, instantiates a new cps_factorial which contains a new unique closure type which instantiates a new cps_factorial...
[1] This is done so that closure calls can be determined statically reducing run-time overhead and helps optimisation.
(However because UP TACK is a mathematical symbol, so Haskell parses it as an Operator and so it must be wrapped in brackets: `(⊥)`)
Although trying that it seems the certificate isn't trusted by iOS Safari.
If I wanted to contact people on messenger they would already have messenger.
trait Copy: Clone {}
Added: Essentially Copy is the same as a move, but the original value is still valid.
I think volatile also means don't change the order with respect to other volatile operations.