Catherine
Catherine
> To avoid exposing Update I would have to add another intermediate struct FrambufferUpdateBuilder and use it like this: Ah. Actually, that wouldn't work because that would still let you...
> How is the send_update supposed to work in this case? It creates a FramebufferUpdate internally and passes a &mut FramebufferUpdate into the closure. This means that a FramebufferUpdate is...
@sj26 this seems to be your change at fault. Care to take a look?
Yeah, I consider that a bug. Unfortunately I've no time to work on it in near future, maybe @bf4 can take a look.
No update since my previous comment. I haven't done any Rails in _years_.
That's how it works, no need to prove anything--the dataseheet actually says that explicitly somewhere, it's just not really clear.
It's implied in this part: 
This should logically be a part of the "functional outline" section, which I've yet to write. Please be patient.
Ah, you're right. I'm now not sure whether I read it somewhere or it was just "obvious" to me.
Certainly it should be attributes? I'm afraid I don't follow you here. Why would it not be safer to use extension nodes?