|
@isislovecruft | |||||
|
is there a word for this pattern? it keeps happening to me
1. start a cool new project
2. start at what seems like a reasonable level
3. realise all the lower level tooling is actually missing
4. build all the tooling
5. *takes forever*
6. actually start the cool new project
|
||||||
|
||||||
|
|
isis agora lovecruft (they/them)
@isislovecruft
|
27. sij |
|
this tweet brought to you by: i have lost count of how many times i've implemented various constant-time comparisons and conditional swaps, and yet, here we are, again pic.twitter.com/BVQIjqmYmo
|
||
|
||
|
|
isis agora lovecruft (they/them)
@isislovecruft
|
27. sij |
|
also before anyone tells me i can optimise this further, yes, i know about the illegal opcodes and that some are useful here, and yes, i know i can save four instructions by removing the subroutines to mask all the bits with the msb, i'm doing it the "simple" way first
|
||
|
|
||
|
Vanessa McHale
@vamchale
|
28. sij |
|
Haskal
|
||
|
|
||
|
|
isis agora lovecruft (they/them)
@isislovecruft
|
28. sij |
|
do.. i.. want to know
|
||
|
|
||
|
Kamil Choudhury
@kchoudhu
|
27. sij |
|
Yak shaving.
|
||
|
|
||
|
|
isis agora lovecruft (they/them)
@isislovecruft
|
27. sij |
|
in this case, i have to do the tooling, there's no choice, i need a bunch of constant-time comparisons and conditional swaps *sigh*
|
||
|
|
||
|
Yaah 🦀 ☕
@yaahc_
|
27. sij |
|
I like to call this "Reasons why I'm working on error handling in rust"
|
||
|
|
||
|
|
isis agora lovecruft (they/them)
@isislovecruft
|
27. sij |
|
huh.. i thought it was so you would have plausible deniability for being @reduct_rs
*ducks to avoid getting hit in the head with a flying mechanical keyboard*
|
||
|
|
||
|
˙Ↄ ʎǝsɐↃ
@squeed
|
27. sij |
|
"Being @mjg59"
|
||
|
|
||
|
|
isis agora lovecruft (they/them)
@isislovecruft
|
27. sij |
|
oh no, what if this is why we get along
|
||
|
|
||