Juraj Kirchheim

It "bounces" macro execution through the compiler. It takes a function that is meant to produce an expression "later". So it registers that function with an id, then it returns...

Ok. I think I sorta understand what you're saying. But you wouldn't happen to have a failing test for the current behavior? ^^

Yeah, in principle I wouldn't mind, but there's that ClassBuilder dependency that's kind of hard to deal with. Ideas?

Probably, yes. I think there was some obscure reason why I went with ClassBuilder in the first place, but I can't remember right now.

Updating states in a binding is generally a bad idea, yes. I'm working on the premise that people reach for it when other options are exhausted, an when they do,...

For map this is quite easy to do. It could indeed be implemented as a `Map`. I wonder if we should have different data structures for different use cases.

> So I mean this should probably be handled at container level Yes and no. First, there should be a standalone functionality that is of type `IncomingRequestHeader->OutgoingReponse->OutgoingResponse` that is able...

Which ones? ^^

Hmm. Off the top of my head, I'd say this can be implemented once in `Client` rather than in each `ClientObject`. Not sure that's better, but it's certainly less work...

Well. For starters we need something to monitor the progress of a source. This looks like it might do the trick: ```haxe class WithProgress extends StreamBase { var data:SourceObject; var...