Matias Fontanini

Good catch, I didn't notice that one. Sounds like a good idea! There's no logging strategy at this point. At some point I wanted to use rdkafka's logging as it...

I think cppkafka could actually log through rdkafka via the configured log callback or `rd_kafka_log_print` (the default) in case there's none. Reopening so I don't forget about this one.

lol at "Reopening so I don't forget about this one.". That looks good. I would probably change "user" to "cppkafka" so it's clear where the error is coming from.

Do you mean implementing the Kafka Streams API in cppkafka? That sounds like a great idea but it's a **lot** of work and I don't have enough time to implement...

Can you be more specific on what you're referring to? What sort of API are you thinking of?

I guess given C++17 has `std::any` and `std::optional` which are the 2 things currently being used by cppkafka, we could optionally allow using these features from namespace std rather than...

This should actually go into the config.h file so that if you build the library, then you must use whatever you used while building. Otherwise you could build cppkafka using...

If you build the library on C++14 and use boost, then you use C++17 on your application and you're using boost then you want this to build as it can...

Constructing `Buffer`s from arbitrary pointers is not allowed unless the type the pointer points to is one byte long. So you can basically write `char`s, `uint8_t`, etc, but writing `float`...

As @accelerated, it's not a good idea to start exposing internals. Also, you can implement your logic yourself: accumulate whatever data you have, when you call flush export it or...