TMI: Back from the outer realms (aka Arizona)

Dear world (including my co-workers): please remind me to not work remote ever if I can avoid it! At least not until rustc gets significantly faster. The reason is that when I have two laptops, I can work on something else while I'm waiting for a build, whereas with only one, I get to... stare into space for 5-ish minutes every time I make a change. "I can just work on the train" only works if I bring two laptops with me. And that just gets awkward. (Yes, I worked all day today on a train going from Los Angeles to San José. Actually, I'm still not even in Paso Robles yet. We have slow trains in my country.)

With that out of my system, today after finishing bug triage (not very eventful; I learned that in the 1500-2000 range, there are a lot of legitimately hard and unfixed bugs, many of which are more like feature requests but not all) I wanted to fix as many open ICEs as I can. There aren't that many of them. Issue 3091 was pretty quick. I just had to make region pointers not a scalar type (they're really not scalar, since they have sub-structure that's visible in the language) and then change all the code that was casting pointers to region pointers to, well, not do that. (This happened only once in the core libs and in a few test cases.) As with so many things (well, not really that many things, I hope) the solution was to introduce library functions that wrap unsafe::reinterpret_cast (which is the equivalent of Haskell's unsafeCoerce). I'm quite proud of the name I came up with for the function that takes an &T to a *T: assimilate (because it makes the pointer forget its region).

( Cut for length )

Actually TMI, unlike my research posts: Volume 2 of the Saga of My Crotch

It's about 7:30 PM and I have another two or three hours to go before the northbound Coast Starlight train I'm on gets to San José. I've done all of the work, and working on the other (much huger) blog post in progress that I'm working on, that I can stand for today. You know what that means, right? It's Surgery TMI O'Clock!

Like with my first surgery post, some disclaimers apply:

1. I like to be open even about things many people consider private, and that means I'm okay with writing about intimate details about my body and my sexuality in public. I'm okay with sharing these details with anyone who might stumble upon them. But you may not be comfortable with reading about them. I'm expecting this will mainly apply to people who know me in particular contexts.
   
   
2. Besides the sexy stuff in here, there's also stuff that's kind of gross, so if you're made easily queasy by blood 'n gore, you might not want to read it either. Seriously, if you don't like reading about pain and some of the grosser things bodies do, don't read it.
   
   
3. Just because I'm sharing these details doesn't mean it's okay to ask any other trans person about surgery they've had, surgery you think they may have had, surgery you think they should have, anything else about surgery, or any intimate details about their bodies that you wouldn't ask someone who wasn't trans who you knew only casually. So don't do that! We're not all alike, and I am not going to be the one who gives any cis people an excuse to ask other trans people invasive questions. In fact, there are a lot of situation in which I don't want to discuss the contents of this post, even with people who I'm comfortable having read it: in the office, in church, on VTA Light Rail, and so on. So use the same judgment you'd use when bringing up any other sensitive topic.
   

If this post doesn't provide TMI about how I relate to my body and about what makes me tick, sexually, then I'll have left something out that I meant to put in, and you'd better nag me about it. It's up to you whether you want to read or not, and so you can decide for yourself, here's a cut tag.

( Read more... )