Philip Kannegaard Hayes
Philip Kannegaard Hayes
wow this looks cool : ) random thought along this line: a "non-determinism checker" option that just executes each iteration twice with the same seed and reports if the traces...
@SSheldon ping in my case, this PR would be handy for interacting with `Virtualization.framework`
Definitely looks similar... One weird thing I'm also noticing: If we make `some-leaf-dep` unconditional ```toml [package] name = "build-only-dep" version = "0.1.0" edition = "2021" # [target.'cfg(unix)'.dependencies] #
cc @abs0luty @programatik29
cc @abs0luty @programatik29 Would be great to get this merged upstream : )
> To be honest, I'm not sure if its preferable to trade the size against an increased risk of heap fragmentation? Did you consider that, and how did you decide...
Sorry, to add on to this, we currently have some layers of async handlers for each `Event` that pass by value. Like: ```rust async fn event_handler.get_ldk_handler_future(event) // 14624 B (!)...
For us at least, I think these (1) max total buffer size, (2) max per-peer buffer size, and (3) max queued lifetime (in timer ticks), are probably Good Enough^tm DoS/QoS...
Sure, you can see how we're using an older version here: https://github.com/lexe-app/lexe-public/blob/master/app-rs/src/client.rs#L300 The `Proxy::custom` callback picks up the most recent Bearer auth token that it needs to send to the...