Daniel Lehenbauer

@alexisfrjp - The key to reproducing this bug is to put the closing ')' on the next line. As you can see, this causes the last variable to be incorrectly...

It's true that high-level code in a safe language like Rust is lowered to unsafe machine instructions for execution. The question I'm interested in is whether, as the module passes...

Good clarification. I was thinking of the two as complimentary, although the two of you are making me realize that there might still be some time pressure to understand how...

Verifiable type/memory safety depends on languages sharing a common type system, like the one introduced by the [GC proposal](https://github.com/WebAssembly/gc). There are inevitable tradeoffs in how completely and efficiently different languages...

One challenge with the way we're currently talking about 'schema-on-read' is that most customers who want schema are looking for a guarantee that their applications/services cannot encounter out-of-schema data. To...

The below strikes me as a good balance between data integrity and dynamic flexibility: **Data Integrity** * There is an explicit schema for the tree expressed as the type of...

@milanro, @dstanesc - Just FYI - Early / experimental draft PR. @dstanesc - I saw that you were experimenting with e2e latency:  Looks like LZ4 continues to be the...

@milanro - You mentioned encryption above. Did you mean compression, or are you interested in encrypting data as well? As an FYI, @noencke is beginning to work on incremental summaries...

We had a two-pronged approach. You were going to explore adding compression and then automatic chunking/deduplication using a rolling hash to achieve incremental summaries in a generic way that works...

@dstanesc - I was intrigued by your remark that LZ4 had less impact on content-defined-chunking. I looked into the LZ4 algorithm a bit and found that the format alternates between...