aauuuggghhh a bunch of euclid stuff requires an impl of Zero, which used to be stdlib but was deprecated, so now it only exists in euclid, so of course fixed doesn't implement it, so inexplicably i can't use TypedRect::max_y
Show this thread
-
-
none of these methods require Zero except from_points, i call shenanigans
2 replies 0 retweets 0 likesShow this thread -
i can't believe i'm being foiled by zero
4 replies 0 retweets 10 likesShow this thread -
the only solutions i see to this are ① wrap fixed in a newtype (kind of sucks, it already sucks that i can't used bare integer literals any more) ② write my own fixed-point type (which tbh i'll half have to do anyway to make division and sqrt work on the gba)
2 replies 0 retweets 2 likesShow this thread -
actually using a newtype will be basically the same amount of a pain in the ass since i'd have to reimplement every impl anyway?
2 replies 0 retweets 0 likesShow this thread -
i thought i'd be defeated by physics but here i am, implementing numbers
6 replies 1 retweet 38 likesShow this thread -
i think i have implemented numbers! but it's hard to tell. also division is almost certainly wrong
3 replies 0 retweets 54 likesShow this thread -
hey is there some magic nightly incantation for setting the optimization level for a particular function, so i can make my byte-slopping fast without wrecking stack traces everywhere
4 replies 0 retweets 2 likesShow this thread -
alternatively i could see about using DMA instead of byte-slopping in the first place.
4 replies 0 retweets 0 likesShow this thread -
wrote 16.16 fixed point, all good tried shifting it to 24.8, lexy is slower ???
2 replies 0 retweets 4 likesShow this thread
Replying to @eevee
Something something power of two?
5:25 PM - 9 Jan 2019
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.