Slava Egorov

The PR was stalled mostly because I was distracted - I will take a landing this code in the monorepo when I get a chance.

Don't use `SynchronousFuture` with `await`. It violates existing `Future` contract and leads to undefined non-portable behavior. Behavior you get on the Web is not correct, `await f` should not resume...

I think the current code is correct. You can only send headers once so they are intentionally reset to `null` after that. You should not be able to enter this...

@owensdj what is the version of the package / Dart SDK you are using?

One possible issue is that here https://github.com/grpc/grpc-dart/blob/master/lib/src/server/handler.dart#L360-L367 `_stream.sendHeaders` can trigger an error at which point `_customHeaders` will end up `null` but `_headersSent` is not `true`. This might be an underlying...

That is correct that we don't see `sendHeaders` in the stack trace, but we see `_sendError` and a bunch of async machinery. It indicates that some sort of error happened...

RE: @rrousselGit > I wonder what the performance overhead would be compared to what you could achieve using code-generation. The performance overhead at which stage and at which mode? If...

@lrhn > I'll absolutely insist that the breaking change policy says that reflection is not supported by any platform class unless it's explicitly stated as being supported. I think this...

@Wdestroier Your Dart code is an order of magnitude less readable than SQL code. Which makes me doubt this sort of use case is something I would want to care...

@Dangling-Feet you don't seem to be providing feedback for this particular proposal and seem to instead propose macro system similar to one which was already explored and shelved for a...