futhark literate. I wanted to do a similar interpretation of
u32in Haskell, but the library I used read the pixel values in big-endian order. This was of course easy to fix, but is this behaviour hardware dependent?
futhark literatedoes the same. I actually didn't give it any thought, and it probably isn't documented.
rgbargba...and since I don't think about endianness that often this gave me some rather confusing results...
I think I've encountered this before but wasn't bothered enough to report it. Unless it is by design for some reason, I think I've found a parsing error, that I assume would be relatively easy to fix.
let a = 0i32 -- |> id
commenting the second line results in a parsing error, this appears to be the case for the
|> operator in particular, not
+ for example. I find it annoying when I comment a
filter for example. A second
-- removes the error.
futhark literateI think it could actually be pretty good for general engineering students.